Help - HTTP Status Codes
HTTP status codes are returned by web servers to indicate the status of a request. The status code is a 3-digit code indicating the particular response. The first digit of this code identifies the class of the status code. The remaining 2 digits correspond to the specific condition within the response class. The following table outlines all status codes defined for the HTTP/1.1 draft specification outlined in IETF rfc 2068.1xx class - Informational
The continue status code tells the browser to continue sending a request to the server.
The server sends this response when the client asks to switch from HTTP/1.0 to HTTP/1.1
2xx class -
This class of status code indicates that the client's request was received, understood, and successful.
The partial content success code is issued when the server fulfills a partial GET request. This happens when the client is downloading a multi-part document or part of a larger file.
3xx class -
This code tells the client that the browser should be redirected to another URL in order to complete the request. This is not an error condition.
4xx class -
This status code indicates that the client has sent bad data or a malformed request to the server. Client errors are generally issued by the webserver when a client tries to gain access to a protected area using a bad username and password.
|405||Method Not Allowed|
|407||Proxy Authentication Required|
|413||Request Entity Too Long|
|414||Request-URI Too Long|
|415||Unsupported Media Type|
5xx class -
This status code indicates that the client's request couldn't be succesfully processed due to some internal error in the web server. These error codes may indicate something is seriously wrong with the web server.
An internal server error has caused the server to abort your request. This is an error condition that may also indicate a misconfiguration with the web server. However, the most common reason for 500 server errors is when you try to execute a script that has syntax errors.
This code is generated by a webserver when the client requests a service that is not implemented on the server. Typically, not implemented codes are returned when a client attempts to POST data to a non-CGI (ie, the form action tag refers to a non-executable file).
The server, when acting as a proxy, issues this response when it receives a bad response from an upstream or support server.
The web server is too busy processing current requests to listen to a new client. This error represents a serious problem with the webserver (normally solved with a reboot).
Gateway timeouts are normally issued by proxy servers when an upstream or support server doesn't respond to a request in a timely fashion.
The server issues this status code when a client tries to talk using an HTTP protocol that the server doesn't support or is configured to ignore.