HTTP Response codes
HTTP Response codesAll,
I’m sure that those involved in web analytics and testing are familiar with tools like HTTPWatch (www.httpwatch.com) and HTTPFox (Firefox Add-in) for testing whether the tagging has been implemented correctly.
However, all I was taught was 200 is good and the rest mean it ain’t worked.
Now previously this was ok with me because I just told the developers to go away and fix is (do it right as per my documentation). However, one day they came back and started speaking in HTTP response codes and I felt that I’d fallen in the nightmare of endless Dilbert cartoons (business versus technical and I was losing badly).
Therefore, I owned up and said “I don’t know” and went away to find the answer. The answer (whilst remaining secret under confidentiality clauses in the contract – hehe) was found on this entry into Wikipedia.
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Miles – thanks for the heads up on this – really useful post (now I can PROVE to the dev team that all is not as it should be!)