TransferLog Directive
Top -
Docs -
General -
Server -
Resource -
Access -
FAQ -
Tutorials
Purpose
The TransferLog directive
tells HTTPd where to record client accesses.
The logfile format is as follows. Each line consists of:
host rfc931 authuser [DD/Mon/YYYY:hh:mm:ss] "request" ddd bbbb "opt_referer" "opt_agent"
- host: Either the DNS name or the IP number of the remote client
- rfc931: Any information returned by identd for this person, - otherwise.
- authuser: If user sent a userid for authentication, the user name, - otherwise.
- DD: Day
- Mon: Month (calendar name)
- YYYY: Year
- hh: hour (24-hour format, the machine's timezone)
- mm: minutes
- ss: seconds
- request: The first line of the HTTP request as sent by the client.
- ddd: the status code returned by the server, - if not available.
- bbbb: the total number of bytes sent, *not including the HTTP/1.0 header*, - if not available
- opt_referer: the referer field if given and if LogOptions is Combined
- opt_agent: the user agent field if given and if LogOptions is Combined
You can determine the name of the file accessed through
request.
Syntax
TransferLog file
file is the name of the file to which transfers will be
logged. It is either a full pathname, or a partial pathname
relative to ServerRoot.
Virtual Host
This directive is valid in virtual host configuration.
Default
If you do not specify a TransferLog, HTTPd assumes:
TransferLog logs/access_log
Compile Option: DEFAULT_XFERLOG
Examples
TransferLog logs/downloads
This logs transfers to the file logs/downloads in the ServerRoot directory.
TransferLog /tmp/httpd-accesses
This logs transfers to the file /tmp/httpd-accesses.
TransferLog /dev/null
This effectively turns off transfer logging.
Return to Server Configuration File Overview
NCSA HTTPd Development Team /
httpd@ncsa.uiuc.edu /
10-02-95