Cisco Cisco Web Security Appliance S660 Guida Utente

Transaction result codes in the access log file describe how the appliance resolves 
client requests. For example, if a request for an object can be resolved from the 
cache, the result code is 

TCP_HIT

. However, if the object is not in the cache and 

the appliance pulls the object from an origin server, the result code is 

TCP_MISS

. 

The following table describes transaction result codes.

TCP_HIT

The object requested was fetched from the disk cache.

TCP_IMS_HIT

The client sent an IMS (If-Modified-Since) request 
for an object and the object was found in the cache. 
The proxy responds with a 304 response.

TCP_MEM_HIT

The object requested was fetched from the memory 
cache.

TCP_MISS

The object was not found in the cache, so it was 
fetched from the origin server.

TCP_REFRESH_HIT

The object was in the cache, but had expired. The 
proxy sent an IMS (If-Modified-Since) request to the 
origin server, and the server confirmed that the object 
has not been modified. Therefore, the appliance 
fetched the object from either the disk or memory 
cache.

TCP_CLIENT_REFRESH_MI

SS

The client sent a “don’t fetch response from cache” 
request by issuing the ‘Pragma: no-cache’ header. 
Due to this header from the client, the appliance 
fetched the object from the origin server.

TCP_DENIED

The client request was denied due to Access Policies.

NONE

There was an error in the transaction. For example, a 
DNS failure or gateway timeout.

FTP_HIT 

The object requested was fetched from the disk cache. 
This is used for native FTP transactions only.

FTP_MEM_HIT 

The object requested was fetched from the memory 
cache. This is used for native FTP transactions only.