iTP Secure WebServer System Administrator's Guide (Version 7.0)

Server Log File Formats
iTP Secure WebServer System Administrator’s Guide—523346-012
C-7
Example
Item values might contain arbitrary characters, including white space (for example,
spaces, tabs, and new lines). Any values containing white space are enclosed by curly
braces. For example:
{WinMosaic/Version 2.0 (ALPHA 2)}
Single (unpaired) instances of brace and backslash characters ( { } \ ) within a value
must be preceded by a backslash (\). Optionally, paired instances of these characters
might be preceded by a backslash. For example:
{Here’s a brace: \{; and another \}; all done!}
Example
This example shows a typical entry in the extended log file:
log {start 793224627.766481} {method GET} {url /~payne}
{bytes 0} {error {file not found}}...
...{status 404} {end 793224627.818003} {host n8kei.tiac.net}
In this example, start, method, url, bytes, error, status, end, and host are
the entry items. Each of these items is immediately followed by the item’s logged
value. For example, the value of method is GET.
Logging through an External ServerClass
During an online transaction, a web client may send customer credentials directly in a
GET request in the URL encoded format. iTP Secure WebServer logs all these
parameters along with sensitive customer information (such as credit/debit card
numbers or CVV numbers) in the webserver log files. This is a security concern,
wherein information must be restricted from being logged in the webserver log files.
security Contains the security protocol being used: either SSLV2, SSLV3,
or PCT.
client-error-dn Contains the distinguished name (DN) of the certificate that is in
error, if client authentication is used and a problem is found while
verifying the client certificate.
client Contains the distinguished name (DN) as taken from the subject field
of the client certificate, if client authentication is used. If client
authentication is requested and not provided, this field is present but
empty.
Note. Future versions of the extended log format might include entries that begin with some
tag other than log. Programs that read log files should be constructed to ignore any
unrecognized tags.
Table C-3. Extended Log Items (page 3 of 3)
Name Description