Help for HTTP errors
134 captures
12 Jan 2010 - 15 Mar 2025
Dec
JAN
Feb
21
2012
2013
2014
success
fail
About this capture
COLLECTED BY
Organization:
Alexa Crawls
Starting in 1996,
Alexa Internet
has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the
Wayback Machine
after an embargo period.
Collection:
Alexa Crawls
Starting in 1996,
Alexa Internet
has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the
Wayback Machine
after an embargo period.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20130121234439/http://www.getnetgoing.com:80/HTTP.html
GetNet
Going
helps make networks work
Internet Explorer
HTTP
Other
Help for HyperText Transfer Protocol (HTTP) errors
Web browsers, such as
Internet Explorer
and Firefox use HTTP to access objects (e.g. web pages and images) on web servers. Whenever the server responds to a browser, it returns a 3 digit numeric status code and a textual “reason phrase”. The status codes are standardized, whereas the reason phrases can vary between servers. The first digit indicates the class of the code (e.g. client or server error), and the remaining digits identify the particular status.
Class
Code
Reason
xx
Client error
400
Bad Request
401
Unauthorized
403
Forbidden
404
Not Found
405
Method Not Allowed
xx
Server error
500
Internal Server Error
501
Not Implemented
502
Bad Gateway
503
Service Unavailable
504
Gateway Timeout
505
HTTP Version not supported
A complete list of official HTTP status codes and reasons
described in RFCs such as [
RFC 2616
Several products report HTTP errors with their own description:
Adobe Flash Media Server
Apache status codes and messages
Microsoft IIS
web servers provide extended numeric status codes.
HTTP headers
You can view them with online tools such as
web-sniffer.net
Extra information
For information about
HTTP versions and specifications, see
HTTP 505: HTTP Version Not Supported
The types of methods for HTTP access, see
HTTP 405: Method Not Allowed
The format of HTTP requests, see
HTTP 400: Bad Request
The format of
addresses (URLs) used to identify web objects
For
a flow chart of how status codes are arrived at
If you're curious about what weird and interesting stuff can appear in HTTP headers, see:
A. Wooster: “
Fun With HTTP Headers
Footnotes
The reasons listed here are the official suggestions from [
RFC 2616
], others are listed in the page about the code.
Copyright (C) 2012 |