iTP Secure WebServer System Administrators Guide (Version 7.5+)

C Server Log File Formats
This appendix describes the formats used in the log files generated by the iTP Secure WebServer:
• “Access Log Format” (page 261)
• “Error Log Format” (page 262)
• “Hypertext Transfer Protocol (HTTP) Status Codes” (page 262)
• “Extended Log Format” (page 264)
• “Logging through an External ServerClass” (page 266)
An entry in these files is structured into a set of distinct components. These components vary by file
type.
Some products and components you use with the iTP Secure WebServer can report configuration,
status, and error messages to other files you specify. For example, the Servlet Server Class (SSC)
reports configuration and status information to the standard output file, and reports error and
exception information to the standard error file. For information about reporting by the SSC, see
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator's Guide.
Access Log Format
The accesslog file records the request history of a server. The information in this file is structured
in the commonlog format (CLF). CLF is used by other Web servers and supports a number of widely
available tools for analyzing logs and generating reports.
The location of the access log file is specified by the AccessLog directive in the server configuration
file. If this directive is not explicitly set, no access log file is generated.
Access Log Entry Format
An entry in the access log file consists of a single line of ASCII text. Each entry logs a single client
request and consists of seven fields of information:
host-nameField 1
-Field 2
user-nameField 3
timeField 4
requestField 5
http-statusField 6
bytes-sentField 7
Table C-1 describes the fields that can appear in an access log entry.
Table 35 Access Log Fields
DescriptionField
Gives the host name of the Web client making a request.
If the Web client’s host name is not available (from the
hostname
Domain Name Server), the server reports the Web client’s
IP address instead.
Reports the Web client user name as identified by the
Internet Authentication Protocol (as defined in RFC 931).
-
The server does not support the Web client user-name field;
it fills this field with a single hyphen (-).
To see RFC 931, use the following URL:
http://www.ietf.org/rfc/rfc931.txt
Access Log Format 261