Squid Access.log The result encoding returned to the client

Tcp_hit

Squid discovers a seemingly fresh copy of the requested resource and sends it immediately to the client.

Tcp_miss

Squid does not request a cache copy of the resource.

Tcp_refersh_hit

Squid discovers a seemingly stale copy of the requested resource and sends a confirmation request to the original server. The original server returned a 304 (unmodified) response, indicating that the copy of squid was still fresh.

Tcp_ref_fail_hit

Squid discovers a seemingly stale copy of the requested resource and sends a confirmation request to the original server. However, the original server failed to respond, or the returned response squid could not be understood. In this case, Squid sends an existing cache copy (most likely stale) to the client.

Tcp_refresh_miss

Squid discovers a seemingly stale copy of the requested resource and sends a confirmation request to the original server. The original server responds to the new content, indicating that the cache copy is indeed stale.

Tcp_client_refresh_miss

Squid found a copy of the requested resource, but the client's request contained the Cache-control:no-cache directive. Squid forwards the client's request to the original server, forcing the cache to confirm.

Tcp_ims_hit

The client sends a confirmation request, and Squid discovers more recent, seemingly fresh copies of the requested resource. Squid sends updated content to the client without contacting the original server.

Tcp_swapfail_miss

Squid discovers a valid copy of the requested resource, but it fails to load it from disk. Squid then sends the request to the original server as if it were a cache loss.

Tcp_negative_hit

Squid also caches this response when a request to the original server causes an HTTP error. Repeated requests for these resources in a short period of time resulted in a no-hit. The NEGATIVE_TTL instruction controls the amount of time these errors are cache. Note that these errors are only in memory cache and will not be written to disk. The following HTTP status codes may cause negative caches (also subject to other constraints): 204, 305, 400, 403, 404, 405, 414, 500, 501, 502, 503, 504.

Tcp_mem_hit

Squid discovers a valid copy of the requested resource in the memory cache and sends it to the client immediately. Note that this is not an accurate representation of all the responses from the Memory service. For example, some caches are in memory, but responses that require confirmation are recorded in Tcp_refresh_hit, Tcp_refresh_miss, and so on.

Tcp_denied

The client's request was rejected because of a http_access or http_reply_access rule. Note the request rejected by Http_access in the 9th field is none/-, however the request is http_reply_access rejected, and there is a valid value in the corresponding place.

Tcp_offline_hit

When Offline_mode is active, SQUID returns a cache hit to any cache response, regardless of its freshness.

Tcp_redirect

The redirector tells Squid to generate an HTTP redirect to the new Uri (see section 11.1). Normally, squid does not record these redirects. If you do this, you must manually define the Log_tcp_redirects pre-processing instructions before compiling the squid.

NONE

Results that are not categorized are used for specific errors, such as invalid host names.

The following labels may appear in the fourth field of the Access.log file, as appropriate for the ICP query.

Udp_hit

Squid found a seemingly fresh copy of the requested resource in the cache.

Udp_miss

Squid did not find a seemingly fresh copy of the requested resource in the cache. If the same target is requested by HTTP, it may be a cache loss. Please compare Udp_miss_nofetch.

Udp_miss_nofetch

Similar to Udp_miss, the difference is that it also indicates that squid is reluctant to handle the corresponding HTTP request. If you use the-y command-line option, Squid will return this label instead of Udp_miss when it starts and compiles its memory index.

Udp_denied

The ICP query was rejected because of the icp_access rule. If more than 95% of the ICP response to a client is udp_denied, and the client database is activated (see Appendix A), Squid stops sending any ICP responses to the client within 1 hours. If this happens, you can also see a warning in cache.log.

Udp_invalid

Squid accepts invalid queries (such as truncated messages, invalid protocol versions, spaces in URIs, and so on). Squid sends Udp_invalid response to the client.

HTTP response Status Code

Table 13-1 lists the digital HTTP response code and justification. Note that squid and other HTTP clients only pay attention to these numeric values. The reason is purely explanatory and does not affect the meaning of the response. For each status code, an index to the specific section of RFC 2616 is also provided. Note that status codes 0 and 600 are non-standard values used by squid and will not be mentioned in the 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
200	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
60S	(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
50W	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
40S	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

This article is from the "12208412" blog, please be sure to keep this source http://12218412.blog.51cto.com/12208412/1869011

Squid Access.log The result encoding returned to the client