Table 13-1列出了数字HTTP响应CODE和理由短句。注意Squid和其他HTTP客户端仅仅关注这些数字值。理由短句是纯解释性的，不会影响响应的意义。对每个状态码，也提供了一个到RFC 2616的具体节的索引。注意状态码0和600是squid使用的非标准的值，不会在RFC里提到。
Table 13-1. HTTP response status codes Code Reason phrase RFC 2616 section
0 No Response Received (Squid-specific) N/A 1xx Informational 10.1 100 Continue
10.1.1 101 Switching Protocols 10.1.2 2xx Successful 10.2 2 00 OK
10.2.1 201 Created 10.2.2 202 Accepted
10.2.3 203 Non-Authoritative Information 10.2.4 204 No Content 10.2.5 205 Reset Content 10.2.6 206 Partial Content 10.2.7 3xx Redirection 10.3 300 Multiple Choices 10.3.1 301 Moved Permanently 10.3.2 302 Found 10.3.3 303 See Other 10.3.4 304 Not Modified 10.3.5 305 Use Proxy 10.3.6 306 (Unused)
10.3.7 307 Temporary Redirect 10.3.8 4xx Client Error 10.4 400 Bad Request 10.4.1 401 Unauthorized 10.4.2 402 Payment Required 10.4.3 403 Forbidden 10.4.4 404 Not Found
10.4.5 405 Method Not Allowed 10.4.6 406 Not Acceptable
10.4.7 407 Proxy Authentication Required 10.4.8 408 Request Timeout 10.4.9 409 Conflict 10.4.10 410 Gone
10.4.11 411 Length Required 10.4.12 412 Precondition Failed
10.4.13 413 Request Entity Too Large
10.4.14 414 Request-URI Too Long 10.4.15 415 Unsupported Media Type
10.4.16 416 Requested Range Not Satisfiable 10.4.17 417 Expectation Failed 10.4.18 5xx Server Error
10.5 500 Internal Server Error 10.5.1 501 Not Implemented 10.5.2 502 Bad Gateway
10.5.3 503 Service Unavailable 10.5.4 504 Gateway Timeout
10.5.5 505 HTTP Version Not Supported
10.5.6 6xx Proxy Error N/A 600 Unparseable Response Headers (Squid-specific) N/A
假如Squid从原始服务器没有接受到任何响应，你可在access.log里看到状态码0。假如Squid接受到的响应没有包含HTTP头部，就会出现状态码600
因篇幅问题不能全部显示，请点此查看更多更全内容