Reply Status Code
Table A-14 shows the percentage of requests for different status codes. Only the popular and possibly interesting status codes are included here.
Table A-14. Reply Status Code Breakdown (IRCache and Anon-U Data)
| Status | IRCache % | Anon-U % |
|---|---|---|
| 200 OK | 59.76 | 71.35 |
| 304 Not Modified | 19.31 | 17.23 |
| 302 Found | 9.27 | 8.12 |
| 504 Gateway Time-out | 5.88 | 0.22 |
| 404 Not Found | 1.46 | 1.21 |
| 403 Forbidden | 1.39 | 0.04 |
| 301 Moved Permanently | 0.50 | 0.48 |
| 500 Internal Server Error | 0.37 | 0.07 |
| 401 Unauthorized | 0.26 | 0.10 |
| 206 Partial Content | 0.08 | 0.05 |
Approximately 20% of all responses are for validation requests where the resource has not changed. Sadly, almost 10% of responses are HTTP redirects (302 status) for pages that have moved to a new location. The high percentage of 504 responses in the IRCache data is from sibling requests that would have resulted in a cache miss. The 206 response code is used for HTTP “range” requests whereby the client requests some subset of the object data. The small percentage of 206 replies is somewhat surprising but perhaps less so given that the data was collected in March of 2000.
Get Web Caching now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
