Technical data

Setting Up HTTP Access Logs
Administration Guide 8-17
auth_user
If the remote client user sent a userid for authentication, the user name;
otherwise “-”
day/month/year:hour:minute:second UTC_offset
Day, calendar month, year and time of day (24-hour format) with the hours
difference between local time and GMT, enclosed in square brackets
"request"
First line of the HTTP request submitted by the remote client enclosed in
double quotes
status
HTTP status code returned by the server, if available; otherwise “-”
bytes
Number of bytes listed as the content-length in the HTTP header, not
including the HTTP header, if known; otherwise “-”
Setting Up HTTP Access Logs by Using Extended Log
Format
WebLogic Server also supports extended log file format, version 1.0, as defined by the
W3C. This is an emerging standard, and WebLogic Server follows the draft
specification from W3C at
www.w3.org/TR/WD-logfile.html. The current
definitive reference may be found from the W3C Technical Reports and Publications
page at
www.w3.org/pub/WWW/TR.
The extended log format allows you to specify the type and order of information
recorded about each HTTP communication. To enable the extended log format, set the
Format attribute on the HTTP tab in the Administration Console to
Extended. (See
step 4. in “Setting Up HTTP Access Logs by Using the Administration Console” on
page 8-15).
You specify what information should be recorded in the log file with directives,
included in the actual log file itself. A directive begins on a new line and starts with a
# sign. If the log file does not exist, a new log file is created with default directives.
However, if the log file already exists when the server starts, it must contain legal
directives at the head of the file.