Browser client's request was accepted, but not yet processed.
The request header did not contain the necessary authentication codes, and the client is denied access.
The web server you're trying to reach is sending back error messages.
There is a syntax error in the request and is denied by the web server.
Too many concurrent web requests for a single file.
The request is missing its Content-Length header.
Your browser request has been completed and the rest of the process can continue.
When new web pages are created by posted form data or by CGI processes, this confirmation message means it worked.
The browser client is not allowed to see a particular file. This can also be returned at times when the server doesn't want any more web visitors.
The server gateway has timed out. Similar to the 408 Timeout error, but this one occurs at the gateway of the server.
The file used to be at that location, but is no longer there.
The HTTP protocol you are asking for is unsupported.
This is a negative response that is usually caused by a problem in programming code when a CGI program is run.
The method you are using to access the file is not allowed.
If the web server is setup properly, it will automatically redirect the reader to the new location of the file.
The web page has been moved temporarily, and a new URL is available. You should be automatically redirected there by the server.
The requested address refers to more than one file. Depending on how the server configuration, you will receive an error or a choice of which page you want.
The info contained in the entity header is not from the original web site, but from a third party server.
The requested file exists but cannot be used as the client system doesn't understand the format the file is configured for.
The requested file was not found on the web server. The file could have been deleted or never existed. This is often caused by misspelling the URL.
The request cannot be carried out by the web server.
When the request header includes an 'if modified since' parameter, this error code will be returned if the file has not changed since that date. Search engine spiders (robots) can generate a lot of these errors.
When you click a link which has no target URL, this response is elicited by the requested server. It's silent and doesn't warn the user about anything.
Standard HTTP response for successful requests.
The requested file wasn't completed downloaded. For example, this message is shown when the user presses the "Stop" button before a page is loaded.
Payment is required. This error code is not yet operational.
A certain configuration is required for this file to be delivered, but the browser client has not set this up.
The web request must be authorized before it can take place.
The requested file was too large to process.
The web server took longer than its time allowed to process the request. This is often caused by heavy web traffic to the server.
The website address (URI) you entered was too long for the server.
This allows the web server to reset any content returned by a CGI.
This error message is a "see other" SRC. The data is somewhere else and the GET method is used to retrieve it.
The service or file that is being requested is currently unavailable.
When requesting a web page, your browser might receive an error status code of 101, followed by an "Upgrade" header showing that the requested server is changing to a different HTTP version.
The file type of the web request is unsupported.
The recipient is expected to repeat the request via the proxy.