HTTP Status Messages

Turn from: http://www.runoob.com/tags/html-httpmessages.html

An error may occur when a browser requests a service from a Web server.

The following list of HTTP status messages that can be returned is listed below: 1xx: Information

message:	Description:
MB Continue	The server receives only a partial request, but once the server does not reject the request, the client should continue to send the remaining requests.
Protocols switching	Server transformation protocol: the server converts requests to a different protocol for compliance with the customer's request.
Checkpoint	Recommendations for recovery requests for put or POST request recovery failures.

2xx: Success

message:	Description:
OK	The request succeeded (this is a standard response to a successful HTTP request). ）
201 Created	The request is created and the new resource is created.
Accepted	The request for processing has been accepted, but processing has not been completed.
203 non-authoritative Information	The request has been successfully processed, but some of the answer headers may be incorrect because a copy of another document is being used.
204 No Content	The request was successfully processed, but no new document was returned. The browser should continue to display the original document. This status code is useful if the user periodically refreshes the page and the servlet can determine that the user's document is new enough.
205 Reset Content	The request was successfully processed, but no new document was returned. However, the browser should reset what it displays. Used to force the browser to clear form input.
206 Partial Content	The customer sends a GET request with a range header, and the server completes it.

3xx: redirect

message:	Description:
Multiple choices	Multiple choices. A list of links. The user can select a link to reach the destination. Up to five addresses are allowed.
Permanently moved	The requested page has been moved to the new URL.
302 Found	The requested page has been temporarily transferred to the new URL.
303 and other	The requested page can be found under a different URL.
304 Not Modified	The document was not modified as expected. The client has a buffered document and makes a conditional request (typically providing a if-modified-since header that indicates that the customer wants to update only a document that is newer than the specified date). The server tells the customer that the previously buffered document can continue to be used.
305 Use Proxy	The document requested by the customer should be extracted through the proxy server specified in the location header.
306 Switch Proxy	is no longer in use, but the code is still preserved.
307 Temporary Redirect	The requested page has been temporarily moved to the new URL.
308 Resume Incomplete	Recommendations for recovery requests for put or POST request recovery failures.

4xx: Client Error

message:	Description:
Bad Request	The server failed to understand the request because of a syntax error.
401 Unauthorized	Legitimate requests, but access to the requested page is prohibited. The client did not provide or failed to authenticate because the requested page requires authentication.
402 Payment Required	This code is not yet available.
403 Forbidden	Legitimate requests, but access to the requested page is prohibited.
404 Not Found	The server was unable to find the requested page.
405 Method Not allowed	The method specified in the request is not allowed.
406 Not acceptable	The server-generated response cannot be accepted by the client.
407 Proxy Authentication Required	The user must first authenticate using a proxy server so that the request is processed.
408 Request Timeout	The request exceeded the server's wait time.
409 Conflict	The request could not be completed because of a conflict.
410 Gone	The requested page is not available.
411 Length Required	"Content-length" is not defined. If there is no such content, the server will not accept the request.
412 Precondition Failed	The prerequisites in the request were evaluated by the server as failed.
413 Request Entity Too Large	The server will not accept requests because the requested entity is too large.
414 Request-uri Too Long	The server will not accept the request because the URL is too long. This occurs when a POST request is converted to a GET request with a lengthy query information.
415 Unsupported Media Type	The server will not accept the request because the media type is not supported.
416 Requested Range not satisfiable	The client requests part of the document, but the server is unable to provide the requested part.
417 Expectation Failed	The server does not meet the request headers specified by the customer in the request.

5xx: Server error

message:	Description:
Internal Server Error	The request was not completed. The server encountered unpredictable conditions.
501 Not implemented	The request was not completed. The server does not support the requested feature, or the service cannot complete the request.
502 Bad Gateway	The request was not completed. When the server acts as a gateway or proxy role, an invalid response is received from the upstream server.
503 Service Unavailable	The server is not currently available (overload or machine).
504 Gateway Timeout	The gateway timed out. The server was unable to receive a timely response from the upstream server when acting as a gateway or proxy role.
505 HTTP Version not supported	The server does not support the HTTP protocol version specified in the request.
511 Network authentication Required	The user needs to provide authentication to obtain a network access entry.