iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Server Log File Formats
iTP Secure WebServer System Administrator’s Guide—522659-001
C-3
Error Log Format
Error Log Format
The error log file records all request and server errors. The information in this file is
structured in the common log format (CLF). CLF is generally used by web servers and
supports a number of widely available tools for analyzing server logs and generating
reports.
The location of the error log file is specified by the ErrorLog directive in the server
configuration file. If this directive is not explicitly set, no error log file is generated.
HyperText Transfer Protocol (HTTP) Status Codes
Table C-2 lists the HTTP status codes that may appear in the extended log file and in the
access log file.
Table C-2. HTTP Status Codes (page 1 of 2)
Status Code Description
100 Continue. The server received the previous part of the request, so the client
should send the next part.
200 Normal result. The request completed without error.
201 Created. A new object was created.
204 No content. The request was processed successfully; the response does not
contain a new document but might contain metainformation to apply to the
current document.
206 Partial content. The server fulfilled a request for a byte range.
301 Moved permanently. The requested resource now resides at a new location.
The request was satisfied by redirection, and any future requests for the
resource should use the new URL.
302 Found/Moved temporarily. The requested resource temporarily resides at a
different location. The request was satisfied by redirection, but any future
requests for the resource should use the original URL.
304 Not modified. The requested object was not modified after the date
specified in the web client’s “If-modified-since” header.
400 Bad request. The web client sent a request the server could not understand.
401 Unauthorized. The request requires authorization (such as a user name and
password) for access to the requested resource.
403 Forbidden. Access to the requested object is not allowed. For example, the
WebServer configuration might restrict access to this region.
404 Not found. The requested object cannot be found on the server, or access
was denied. For example, the WebServer configuration might restrict
access to this region; several configuration commands have a -noexist
option, causing the server to report that the file was not found, rather than
that access was denied.