210 likes | 582 Views
Common Log Format. a RFC 931 describes the ident lookup used in this authentication. The ident protocol was discussed in Ch5. Common Log Format (cont.). Combined Log Format. An Example of a Combined Log Format entry. 209.1.32.44 – [03/Oct/1999:14:16:00 -0400] “ GET / HTTP/1.0 ” 200 1024
E N D
Common Log Format a RFC 931 describes the ident lookup used in this authentication. The ident protocol was discussed in Ch5.
An Example of a Combined Log Format entry 209.1.32.44 – [03/Oct/1999:14:16:00 -0400] “GET / HTTP/1.0” 200 1024 http://www.joes-hardware.com/“5.0: Mozilla/4.0 (compatible; MSIE 5.0; Window 98)” The Referer and User-Agent fields are assigned as follows:
Netscape Extended 2 Log Format (cont.) • Netscape route codes :
Netscape Extended 2 Log Format (cont.) • Netscape finish status codes
Netscape Extended 2 Log Format (cont.) • Netscape cache codes :
Squid Proxy Log Format (cont.) • Squid result codes
Squid Proxy Log Format (cont.) • Squid result codes (cont.) :
http://hrrpd.apache.org/docs/logs.html “Apache HTTP Server: Log Files.” http://www.squid-cache.org/Doc/FAQ/FAQ-6.html “Squid Log Files.” http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format “Logging Control in W3C httpd” http://www.w3.org/TR/WD-logfile.html “Extended Log File Format” http://www.ietf.org/rfc/rfc2227.txt RFC 2227, “Simple Hit-Metering and Usage-Limiting for HTTP” For More Information