Posted by: Jerry Lees
HTTP, HTTP Status Codes, http tools, Web applications, Web Pages, web sites, web tools, webmaster
As a web administrator I encounter quite a few instances where a weird HTTP status is returned to a browser.Even using them often it’s hard to remember the codes 100% and what they all mean. Sure, a 404 means the file doesn’t exist and a 200 is a good response… but what about the harder more obscure ones? Generally the toughest to resolve revolve around permissions and the HTTP 401.x status, here is a good article explaining the HTTP 401 sub status codes for IIS (The general idea will flow over to other web servers like apache as well).
As a added bonus here is a great article that explains a vast variety of other HTTP Status codes.