What are the cache hit/miss codes results for a cacheflow and Edge SWG (ProxySG) access logs
search cancel

What are the cache hit/miss codes results for a cacheflow and Edge SWG (ProxySG) access logs

book

Article ID: 167160

calendar_today

Updated On:

Products

CF-5000 ProxySG Software - SGOS Advanced Secure Gateway Software - ASG

Issue/Introduction

The cache hit/miss code results for CacheFlow and ProxySG access logs are similar; however, ProxySG has a few more values than CacheFlow.


The following are the shared action field values for an access log from CacheFlow and ProxySG:
 

DENIEDPolicy denies a method.
FAILEDAn error or failure occurred.
TUNNELEDSuccessful data transfer operation.
TCP_SWAPFAILThe object was believed to be in the cache, but could not be accessed.
TCP_HITA valid copy of the requested object was in the cache.
TCP_HIT_RST A valid copy of the requested object was in the cache, but the client connection was reset before the complete response was delivered.
TCP_MEM_HITThe requested object was, in its entirety, in RAM.
TCP_RESCAN_HITThe requested object was found in the cache but was rescanned because the virus-scanner-tag-id in the object was different from the current scanner tag.
TCP_RESCAN_HIT_RSTThe requested object was rescanned (see TCP_RESCAN_HIT) but the client connection was reset before the complete response was delivered.
TCP_AUTH_HITThe requested object requires upstream authentication, and was served from the cache.
TCP_AUTH_HIT_RSTThe requested object requires upstream authentication, but the client connection was reset before the complete response was delivered.
TCP_RESUMED_HITThe cache contained an incomplete object. Part of the request was served from cache and the OCS was contacted to retrieve the rest.
TCP_RESUMED_HIT_RSTThe cache contained an incomplete object. Part of the request was served from cache and the OCS was contacted to retrieve the rest. However the client connection was reset before the data was returned.
TCP_MISSThe requested object was not in the cache.
TCP_MISS_RSTThe requested object was not in the cache; the client connection was reset before the complete response was delivered.
TCP_REFRESH_HITA GIMS request to the server was forced and the response was 304 Not Modified; this appears in the Statistics:Efficiency file as In Cache, verified Fresh.
TCP_REFRESH_HIT_RSTA GIMS request to the server was forced and the response was 304 Not Modified; the client connection was reset before the complete response was delivered.
TCP_CLIENT_REFRESHThe client forces a revalidation with the origin server with a Pragma: no-cache. If the server returns 304 Not Modified, this appears in the Statistics:Efficiency file as In Cache, verified Fresh.
TCP_CLIENT_REFRESH_RSTThe client forces a revalidation with the origin server, but the client connection was reset before the complete response was delivered.
TCP_REFRESH_MISSA GIMS request to the server was forced and new content was returned.
TCP_REFRESH_MISS_RSTA GIMS request to the server was forced and new content was returned, but the client connection was reset before the content returned.
TCP_PARTIAL_MISSThe object is in the cache, but retrieval from the origin server is in progress.
TCP_PARTIAL_MISS_RST The object is in the cache, but retrieval from the origin server is in progress; the client connection was reset before the complete response was delivered. 
TCP_RESUMED_MISSThe cache contained an incomplete object, that is out of date. The cache was reaquired the object from the OCS.
TCP_RESUMED_MISS_RSTThe cache contained an incomplete object, that is out of date. The cache reacquired the object from the OCS. However the client connection was reset before the object was delivered.
TCP_AUTH_MISSThe requested object requires upstream authentication, and was not served from the cache. This is part of CAD (Cached Authenticated Data).
TCP_AUTH_MISS_RSTThe requested object requires upstream authentication, and was not served from the cache; the client connection was reset before the complete response was delivered.
TCP_NC_MISSThe object returned from the origin server was noncacheable.
TCP_NC_MISS_RSTThe object returned from the origin server was noncacheable; the client connection was reset before the complete response was delivered.
TCP_NC_EXCLUDEDThe object was non-cacheable because of an exclude() gesture in policy.
TCP_NC_EXCLUDED_RSTThe object was non-cacheable because of an exclude() gesture in policy. However before the object could be returned the client connection was reset.
TCP_TUNNELEDThe CONNECT method was used to tunnel this request (generally proxied HTTPS).
TCP_ACCELERATEDFor CONNECT tunnels that are handed off to the following proxies: HTTP, SSL, Endpoint mapper, and P2P for BitTorrent/EDonkey/Gnutella.
TCP_DENIEDAccess to the requested object was denied by a filter.
TCP_SPLASHEDThe user was redirected to a splash page.
TCP_AUTH_REDIRECTThe client was redirected to another URL for authentication.
TCP_AUTH_FORMForms-based authentication is being used and a form challenging the user for credentials is served in place of the requested content. Note: Upon submission of the form, another access log entry is generated to indicate the status of the initial request.
TCP_POLICY_REDIRECTThe client was redirected to another URL due to policy.
TCP_ERR_MISSAn error occurred while retrieving the object from the origin server.
TCP_LOOPThe current connection is dropped because the upstream connection would result in a looped connection.






The following are additional action field values for an access log from ProxySG:
 

ALLOWEDAn FTP method (other than the data transfer method) is successful.
SUCCESSThe request was completed.
ACCELERATEDAn FTP method (other than the data transfer method) is successful.
BATCHEDThe request was batched.
SERVER_ERRORThe request returned with and error and the request was denied.
CACHE_HITThe object request was complete from the cache without a trip to the origin server.
CACHE_MISSThe object request was not found in the cache. The ProxySG must then fetch the requested object from the origin server.
LICENSE_EXPIRED(SOCKS only) The request could not be handled because the associated license has expired.
TCP_WEBSOCKETThe request was a WebSocket upgrade request. You can determine if the traffic was plain WebSocket or secure WebSocket by looking at the scheme (HTTP or HTTPS).
TCP_BYPASSEDA TCP-Tunneled connection was bypassed because an upstream ADN concentrator was not discovered; this can occur only when the bypass-if-no-concentrator feature is enabled and all conditions for activating the feature are met.
TCP_POLICY_REDIRECTThe client was redirected to another URL due to policy.
UDO_HITA valid copy of the requested object was in the cache. This value is also used with ICP queries.
UDP_OBJAn ICP request was made to this cache for an object that was in the cache, and the object was returned through UDP.
UDP_MISSThe requested object was not in the cache. This value is also used with ICP queries.
UDP_MISS_NOFETCHAn ICP request was made to this cache for an object not in the cache.The requester was informed that it could not use this cache as a parent to retrieve the object.
UDP_INVALIDThe ICP request was corrupt, short, or otherwise unintelligible.
UDP_DENIEDAccess was denied for this request.
UDP_LOOPAn ICP request was dropped because the upstream connection would result in a looped connection.

Resolution

Refer the table above.