Cisco Cisco Web Security Appliance S390 Betriebsanweisung

438

I R O N P O R T   A S Y N C O S   6 . 3   F O R   W E B   U S E R   G U I D E  

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.

RoutingPolicyGroup

 

Routing Policy group name as ProxyGroupName/
ProxyServerName

.

When the transaction matches the global Routing Policy, 
this value is “DefaultRouting.” When no upstream proxy 
server is used, this value is “DIRECT.”
Any space in the policy group name is replaced with an 
underscore ( _ ).

<IW_misc,9.9,-,-,-,-,-,-,-
,-,-,-,-,-,-,IW_misc,->

Web Reputation filtering and Anti-Malware scanning 
information.
For more information about the values included within the 
angled brackets, see “Understanding Web Reputation and 
Anti-Malware Information” on page 442.

Table 20-6 Transaction Result Codes

Result Code

Description

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.

Table 20-5 Access Log File Entry (Continued)

Field Value

Field Description