Home - Publications - Articles - The Zen of Serving Web Pages - Nine Aspects of a Web Log Entry - Result Code

After the Storm - Internet Technologies

Home
Publications
Articles
The Zen of Serving Web Pages
The Connection between Browser and Server
What Sound Does a Web Hit Make?
Nine Aspects of a Web Log Entry
Host
User
Login
Date and Time
Command
Result Code
Bytes Transfered
Referer
Agent
The Philosophy of Hits, Views, and Visits
How to Recognize a Human Being
Words and Their Meaning

Result Code

What is is.

The result code as returned by the web server (RFC 2616).

What it says.

It tells you how the processing of the request went. The codes are grouped into classes:

  • 1xx "Informational" (more result codes might follow)
  • 2xx "Successful" (the document has been sent)
  • 3xx "Redirection" (the document has not been sent, and the browser gets instructed to load a different URL instead)
  • 4xx "Client Error" (the document can't be sent because i.e. it does not exist)
  • 5xx "Server error" (the document can't be sent because the server has a bad time)

What may cause trouble.

The question is which log entries should make into which reports? When you're looking at hits, should that include URLs that couldn't be served (client or server error)? Or how about redirections: should hits appear under the originial URL? The redirected URL? Both?

© 1998-2005 Christian Treber, ct@ctreber.com. All rights reserved. The author takes no responsability for linked external pages, the content of which by no means reflect his own opinion, convictions etc.