Cisco Cisco Web Security Appliance S390 Guida Utente
24-51
Cisco IronPort AsyncOS 7.1 for Web User Guide
OL-23207-01
Chapter 24 Logging
Including HTTP/HTTPS Headers in Log Files
Note
You can create a custom field for any header in a client request or a server
response. For more information, see
response. For more information, see
.
Including HTTP/HTTPS Headers in Log Files
If the list of predefined access log and W3C log fields does not include all header
information you want to log from HTTP/HTTPS transactions, you can type a user
defined log field in the Custom Fields text box when you configure the access and
W3C log subscriptions.
information you want to log from HTTP/HTTPS transactions, you can type a user
defined log field in the Custom Fields text box when you configure the access and
W3C log subscriptions.
Custom log fields can be any data from any header sent from the client or the
server. If a request or response does not include the header added to the log
subscription, the log file includes a hyphen as the log field value.
server. If a request or response does not include the header added to the log
subscription, the log file includes a hyphen as the log field value.
defines the syntax to use for access and W3C logs.
For example, if you want to log the If-Modified-Since header value in client
requests, enter the following text in the Custom Fields box for a W3C log
subscription:
requests, enter the following text in the Custom Fields box for a W3C log
subscription:
cs(If-Modified-Since)
Table 24-12
Configuring HTTP/HTTPS Headers in Log Files
Header Type
Access Log Format
Specifier Syntax
Specifier Syntax
W3C Log Custom Field Syntax
Header from the
client application
client application
%<ClientHeaderName:
cs(ClientHeaderName)
Header from the
server
server
%<ServerHeaderName: sc(ServerHeaderName)