(1) TCP_HIT, TCP_MEM_HIT
요청한 컨텐츠가 캐시에 있어서 응답한 경우
(2) TCP_MISS
요청한 컨텐츠가 캐시에 없어서 실제 서버로 요청을 하여 응답한 경우
(3) TCP_IMS_HIT
클라이언트가 If-Modified-Since 필드를 요청 헤더에 보냈는데 HIT가 났다는 의미이다.
만약 결과 HTTP코드값이 '304 Not Modified'로 나왔다면 캐시는
클라이언트로 컨텐츠를 보낼 필요없이 클라이언트 브라우저에 있는 컨텐츠를 사용한다는 의미이다.
(4) TCP_IMS_MISS
요청헤더에 If-Modified-Since 가 포함되어 있지만 캐시가 신선하지 않다고 판단되어 실제 서버로 재요청을 한 경우
(5) TCP_REFRESH_HIT
요청한 컨텐츠가 신선하지 않아 실제 서버로 요청했는데 '304 Not Modified'를 받아 캐시에서 클라이언트로 응답한 경우
(6) TCP_REFRESH_MISS
요청한 컨텐츠가 신선하지 않아 실제 서버로 요청했는데
서버에서 새로운 컨텐츠를 전송받아 캐시에 저장하고 다시 클라이언트로 응답
(7) TCP_CLIENT_REFRESH
클라이언트 요청 헤더에 'no_cache'를 포함한 경우
(8) TCP_CLIENT_REFRESH_MISS
클라이언트 요청에 'no-cache'나 'no-store'같은 캐시를 제어하는 필드를 포함하여서
캐시가 서버로부터 컨텐츠를 가져왔을때
(9) TCP_DENIED
클라이언트 요청이 캐시에 의해서 거절당했을 경우(컨텐츠필터링과 연관)
TCP_ codes
Note, TCP_ refers to requests on the HTTP port (3128).
- TCP_HIT
-
A valid copy of the requested object was in the cache.
-
- TCP_MEM_HIT
-
A valid copy of the requested object was in the cache, AND it was in memory so it did not have to be read from disk.
-
- TCP_NEGATIVE_HIT
-
The request was for a negatively-cached object. Negative-caching refers to caching certain types of errors, such as "404 Not Found." The amount of time these errors are cached is controlled with the negative_ttl configuration parameter.
-
- TCP_MISS
-
The requested object was not in the cache.
-
- TCP_REFRESH_HIT
-
The object was in the cache, but STALE. An If-Modified-Since request was made and a "304 Not Modified" reply was received.
-
- TCP_REF_FAIL_HIT
-
The object was in the cache, but STALE. The request to validate the object failed, so the old (stale) object was returned.
-
- TCP_REFRESH_MISS
-
The object was in the cache, but STALE. An If-Modified-Since request was made and the reply contained new content.
-
- TCP_CLIENT_REFRESH
-
The client issued a request with the "no-cache" pragma.
-
- TCP_IMS_HIT
-
The client issued an If-Modified-Since request and the object was in the cache and still fresh.
-
- TCP_IMS_MISS
-
The client issued an If-Modified-Since request for a stale object.
-
- TCP_SWAPFAIL
-
The object was believed to be in the cache, but could not be accessed.
-
- TCP_DENIED
-
Access was denied for this request
UDP_ codes
"UDP_" refers to requests on the ICP port (3130)
- UDP_HIT
-
A valid copy of the requested object was in the cache.
-
- UDP_HIT_OBJ
-
Same as UDP_HIT, but the object data was small enough to be sent in the UDP reply packet. Saves the following TCP request.
-
- UDP_MISS
-
The requested object was not in the cache.
-
- UDP_DENIED
-
Access was denied for this request.
-
- UDP_INVALID
-
An invalid request was received.
-
- UDP_RELOADING
-
The ICP request was "refused" because the cache is busy reloading its metadata.
ERR_ codes
"ERR_" refers to various types of errors for HTTP requests. For example:
- ERR_CLIENT_ABORT
-
The client aborted its request.
-
- ERR_NO_CLIENTS
-
There are no clients requesting this URL any more.
-
- ERR_READ_ERROR
-
There was a read(2) error while retrieving this object.
-
- ERR_CONNECT_FAIL
-
Squid failed to connect to the server for this request.
Hierarchy Data Tags
- DIRECT
-
The object has been requested from the origin server.
-
- FIREWALL_IP_DIRECT
-
The object has been requested from the origin server because the origin host IP address is inside your firewall.
-
- FIRST_PARENT_MISS
-
The object has been requested from the parent cache with the fastest weighted round trip time.
-
- FIRST_UP_PARENT
-
The object has been requested from the first available parent in your list.
-
- LOCAL_IP_DIRECT
-
The object has been requested from the origin server because the origin host IP address matched your 'local_ip' list.
-
- SIBLING_HIT
-
The object was requested from a sibling cache which replied with a UDP_HIT.
-
- NO_DIRECT_FAIL
-
The object could not be requested because of firewall restrictions and no parent caches were available.
-
- NO_PARENT_DIRECT
-
The object was requested from the origin server because no parent caches exist for the URL.
-
- PARENT_HIT
-
The object was requested from a parent cache which replied with a UDP_HIT.
-
- SINGLE_PARENT
-
The object was requested from the only parent cache appropriate for this URL.
-
- SOURCE_FASTEST
-
The object was requested from the origin server because the 'source_ping' reply arrived first.
-
- PARENT_UDP_HIT_OBJ
-
The object was received in a UDP_HIT_OBJ reply from a parent cache.
-
- SIBLING_UDP_HIT_OBJ
-
The object was received in a UDP_HIT_OBJ reply from a sibling cache.
-
- PASSTHROUGH_PARENT
-
The neighbor or proxy defined in the config option 'passthrough_proxy' was used.
-
- SSL_PARENT_MISS
-
The neighbor or proxy defined in the config option 'ssl_proxy' was used.
-
- DEFAULT_PARENT
-
No ICP queries were sent to any parent caches. This parent was chosen because it was marked as 'default' in the config file.
-
- ROUNDROBIN_PARENT
-
No ICP queries were received from any parent caches. This parent was chosen because it was marked as 'default' in the config file and it had the lowest round-robin use count.
-
- CLOSEST_PARENT_MISS
-
This parent was selected because it included the lowest RTT measurement to the origin server. This only appears with 'query_icmp on' set in the config file.
-
- CLOSEST_DIRECT
-
The object was fetched directly from the origin server because this cache measured a lower RTT than any of the parent caches.
Almost any of these may be preceded by 'TIMEOUT_' if the two-second (default) timeout occurs waiting for all ICP replies to arrive from neighbors.
