Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Working With Log Files > Example event log file entries > Cache result codes in Squid- and Netscape-format log files
Cache result codes in Squid- and Netscape-format log files
Help | Content Gateway | v8.5.x
Cache result codes in the Squid and Netscape log files:
 
Cache Result Code
Description
TCP_HIT
Indicates that a valid copy of the requested object was in the cache and that the proxy sent the object to the client.
TCP_MISS
Indicates that the requested object was not in the cache and that the proxy retrieved the object from the origin server or from a parent proxy and sent it to the client.
TCP_REFRESH_HIT
Indicates that the object was in the cache but was stale. Content Gateway made an if-modified-since request to the origin server and the origin server sent a 304 not-modified response. The proxy sent the cached object to the client.
TCP_REF_FAIL_HIT
Indicates that the object was in the cache but was stale. Content Gateway made an if-modified-since request to the origin server but the server did not respond. The proxy sent the cached object to the client.
TCP_REFRESH_MISS
Indicates that the object was in the cache but was stale. Content Gateway made an if-modified-since request to the origin server and the server returned a new object. The proxy served the new object to the client.
TCP_CLIENT_REFRESH
Indicates that the client issued a request with a no-cache header. The proxy obtained the requested object from the origin server and sent a copy to the client. Content Gateway refreshes any previous copy of the object in the cache.
TCP_IMS_HIT
Indicates that the client issued an if-modified-since request and the object was in the cache and fresher than the IMS date, or an if-modified-since to the origin server found that the cache object was fresh. The proxy served the cached object to the client.
TCP_IMS_MISS
Indicates that the client issued an if-modified-since request and the object was either not in cache or was stale in cache. The proxy sent an if-modified-since request to the origin server and received the new object. The proxy sent the updated object to the client.
TCP_SWAPFAIL
Indicates that the object was in the cache but could not be accessed. The client did not receive the object.
ERR_CLIENT_ABORT
Indicates that the client disconnected before the complete object was sent.
ERR_CONNECT_FAIL
Indicates that Content Gateway could not reach the origin server.
ERR_DNS_FAIL
Indicates that the Domain Name Server could not resolve the origin server name, or that no Domain Name Server could be reached.
ERR_INVALID_REQ
Indicates that the client HTTP request was invalid. Content Gateway forwards requests with unknown methods to the origin server.
ERR_READ_TIMEOUT
Indicates that the origin server did not respond to the Content Gateway request within the timeout interval.
ERR_PROXY_DENIED
Indicates that client service was denied by access control configuration.
ERR_UNKNOWN
Indicates that the client connected but subsequently disconnected without sending a request.
 

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Working With Log Files > Example event log file entries > Cache result codes in Squid- and Netscape-format log files
Copyright 2023 Forcepoint. All rights reserved.