Wordpress Blog Installation Service!

Understanding Web Statistics Part III – Understanding Server Response Codes

Posted by Zulfikar under Statistics

Response codes (also called status codes) are the coded results of a server’s attempt to understand and satisfy a request. Web server responses indicate whether a Web object (Web page, graphics file, CGI script, etc.) was successfully retrieved or executed and, if not, the reason for the unsuccessful result. Unsuccessful results are also referred to as server error codes.

Log files record these codes, and the Visitor Statistics tool includes a report on them.

The following codes are some of the most common responses:

* Code 200 – OK: The request was fulfilled. The Web page was successfully downloaded without error.

Notes: In the strictest sense this not an error but a confirmation that things are working just fine.

* Code 401 – Unauthorized: The code indicates that users have tried to access pages that are restricted to a private network or IP address.

* Code 404 – Not Found: The server has not found anything matching the URL given, which can indicate broken links in the Website due to the removal of a Web page or other resource. Alternatively, the response may indicate spelling errors in the URL.

Notes: This can be and is a very annoying error both for the site owner and the visitors. As a site owner you stand to loose your readers as well as PR link juice. For readers who are repeat visitors this can be very frustrating and more so if the page/post they are trying to access has very important information.

Tip: It is a good idea to code your 404 page to redirect your visitors to the main/home page should there be an error, be it a site error or a mistyped or misspelled URL. – If there is indeed a site error and you are aware of it then its a good idea to let your readers know and reassure them that you are doing everything possible to resolve it.

* Code 403- Forbidden: The request is for something forbidden. The code indicates that users have tried to access pages that require user authorization, such as password-protected administration areas or members areas.

Notes: If there are no pages/post requiring such authentication then you need to check your site for unwanted scripts and to avoid reader frustration.

* Code 500 – Internal Error: The request failed. The server encountered an unexpected condition which prevented it from fulfilling the request. This code often indicates a script error.

Note: 9 times out of 10 this error is related to the .htaccess. It’s a good idea to check your site and analyse the .htaccess to make sure it only contains the codes it is supposed to. If you are not familiar with the .htaccess codes, renaming the file and generating a fresh (if your site script settings are capable) one usually helps resolve the problem.

If all else fails, consult an expert.

More readings:

If not already done so, read Understanding website statistics part I and Understanding website statistics part II

The w3.org site has more detailed information on all error codes – check out the list at http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Share your views and experience related to this topic, please leave a comment. If you have any tips, would love to hear them

Related posts:

1. Understanding Web Statistics Part II – Visitor Activity!
2. 7 Easy Steps To Understanding Web Statistics
3. No More Excuses: Blogging Can Be THIS Easy