1. Common Log Format Field Description
a RFC 931 describes the ident lookup used in this authentication. The ident protocol was discussed in Ch5.

2. Common Log Format (cont.)

3. Combined Log Format Field Description Referer
The contents of the Referer HTTP header
User-Agent
The contents of the User-Agent HTTP header

4. An Example of a Combined Log Format entry
– [03/Oct/1999:14:16: ] “GET / HTTP/1.0”
“5.0: Mozilla/4.0 (compatible; MSIE 5.0;
Window 98)”
The Referer and User-Agent fields are assigned as follows:
Field
Value
Referer
User-Agent
5.0:Mozilla/4.0 (compatible; MSIE 5.0;Windows98)

5. Netscape Extended Log Format
Field
Description

6. Netscape Extended Log Format (cont.)
Field
Value

7. Netscape Extended 2 Log Format
Field
Description

8. Netscape Extended 2 Log Format (cont.)
Field
Value

9. Netscape Extended 2 Log Format (cont.)
Netscape route codes :
Value
Description
DIRECT
The resource was fetched directly from the server
PROXY (host:port)
The resource was fetched throuh the proxy “host.”
SOCKS (socks:port)
The resource was fetched through the SOCKS server “host.”

10. Netscape Extended 2 Log Format (cont.)
Netscape finish status codes
Value
Description

11. Netscape Extended 2 Log Format (cont.)
Netscape cache codes :
Code
Description

12. Squid Proxy Log Format
Field
Description

13. Squid Proxy Log Format (cont.)
Field
Description

14. Squid Proxy Log Format (cont.)
Squid result codes
Action
Description

15. Squid Proxy Log Format (cont.)
Squid result codes (cont.) :
Action
Description

16. The Meter Header
Directive
Abbreviation
Who
Description

17. The Meter Header (cont.)

18. For More Information http://hrrpd.apache.org/docs/logs.html
“Apache HTTP Server: Log Files.”
“Squid Log Files.”
“Logging Control in W3C httpd”
“Extended Log File Format”
RFC 2227, “Simple Hit-Metering and Usage-Limiting for HTTP”