[an error occurred while processing this directive]

Access Log in Common Log Format

Access logs in the Extended Common Log Format contain all web accesses associated with a specific hostname in a standardized format. You also have the option of having your accesses stored in a WebCom log file format logs (which are more readable) or in both formats.

To activate logging in common log format, a directory named "clogs" must be created in your home directory. Our system will automatically create subdirectories which correspond to each hostname associated with your account. For example, if people access your account through three hostnames, "www.domain.com", "domain.com" and "www.seconddomain.com" you will find three directories with those respective names.

Access to both domain.com and www.domain.com load the same web pages. However, our logging system records the information as to which URL was used, so accesses to domain.com show up in one directory, and accesses to www.domain.com will show up in another directory. This is to provide customers a high level of detail with which to analyze site traffic.

In each of these subdirectories our system will create an access file for that hostname named "log". If you delete this file, it is automatically recreated the next time that accesses are recorded, unless you delete the entire "clogs" directory as well. (NOTE: There may be a delay before logging begins; the system only checks for the addition of a logs directory periodically.)

IMPORTANT NOTE: Our system does not automatically delete, remove, or overwrite clogs files. If you configure your account to generate clog files, the logs will accumulate indefinitely. Be sure to download and delete these files periodically, as unchecked log files can take up a lot of your diskspace quota. If your clog files becomes too large for you to be able to download, you can compress this file when downloading it.


Here's what your personal access log in common log format looks like: 
pglab39.pg.cc.md.us - - [13/Mar/1995:09:09:03 -0800] "GET /webcom/gstbk.html HTTP/1.0" 200 35727 "http://webcom.com/~webcom/cgi-bin/cust_sites" "Mozilla/3.0 (Win95; I)"
pglab39.pg.cc.md.us - - [13/Mar/1995:09:17:18 -0800] "GET /webcom/gstbk.html HTTP/1.0" 304 0 "/gstbk.html" "Mozilla/3.0 (Win95; I)"
xroads.wr.usgs.gov - - [13/Mar/1995:09:17:53 -0800] "GET /webcom/order.html HTTP/1.0" 200 2344 "" "Mozilla/3.0 (Macintosh; I; PPC)"
148.241.22.29 - - [13/Mar/1995:09:21:09 -0800] "GET /webcom/order.html HTTP/1.0" 200 2344 "http://www.lycos.com/" "Mozilla/3.0Gold (Win95; U)"
nameless.house.gov - - [13/Mar/1995:10:00:30 -0800] "GET /webcom/graphics/hp.gif HTTP/1.0" 200 2690 "/order.html" "Mozilla/3.0 (Macintosh; I; PPC)"
splitter.amnh.org - - [13/Mar/1995:10:01:10 -0800] "GET /webcom/order.html HTTP/1.0" 200 2344 "http://webcom.com/~webcom/" "Mozilla/3.0 (Win95; I)"

The format of the common log file: 

remotehost rfc931 authuser [date] "request" status bytes "referrer" "user_agent"

remotehost
Remote hostname (or IP number if DNS hostname is not available).
rfc931
The remote login name of the user (this feature is not available on the WebCom server for technical reasons).
authuser
The username as which the user has authenticated himself. This is only available when using Access Authorization (password protected WWW pages).
[date]
Date and time of the request.
"request"
The request line exactly as it came from the client (i.e., the file name, and the method used to retrieve it [GET in 99% of the cases]).
status
The HTTP status code returned to the client. Whether or not the file was successfully retrieved, and if not, what error message was returned.
bytes
The content-length of the document transferred.
"referrer"
The previous URL visited by the accessor
"user_agent"
Information about the browser used to access
[an error occurred while processing this directive]