Http response status code and response code

Http response status code (transfer) and response code

Http status return code 1xx (temporary response)
Status Code indicating a temporary response and requiring the requester to continue the operation.

Http status return code:

Code Description
100 (CONTINUE) the requester shall continue to make the request. The server returns this code, indicating that the first part of the request has been received and is waiting for the remaining part.
101 (switching protocol) the requester has requested the server switching protocol. The server has confirmed and is ready to switch.

Http status return code2xx (successful)
Indicates that the request status code is successfully processed.

Http status return code

Code Description
200 (successful) the server has successfully processed the request. Generally, this indicates that the server provides the requested webpage.
The 201 (created) request is successful and the server creates a new resource.
202 (accepted) the server has accepted the request but has not yet processed it.
203 (unauthorized information) the server has successfully processed the request, but the returned information may come from another source.
204 (NO content) The server successfully processed the request, but did not return any content.
205 (reset content) The server successfully processed the request, but did not return any content.
206 (partial content) The server successfully processes some GET requests.

Http status return code3xx (redirection)
Indicates that further operations are required to complete the request. These status codes are usually used for redirection.

Http status return code

Code Description
300 (multiple options) for requests, the server can perform multiple operations. The server selects an operation based on the user agent or provides an operation list for the user agent to select.
The webpage of the 301 (permanent mobile) request has been permanently moved to a new location. When the server returns this response (response to a GET or HEAD request), it automatically redirects the requester to a new location.
The 302 (temporary mobile) server currently responds to requests from different locations, but the requester should continue to use the original location for subsequent requests.
303 (view other locations) when the requester uses a separate GET request for different locations to retrieve the response, the server returns this code.

304 (not modified) the requested webpage has not been modified since the last request. When the server returns this response, no webpage content is returned.
305 (using a proxy) the requester can only use a proxy to access the requested webpage. If the server returns this response, it also indicates that the requester should use a proxy.
307 (temporary redirection) The server currently responds to requests from different locations, but the requester should continue to use the original location for subsequent requests.

Http status return code4xx (request error)
These status codes indicate that the request may fail and impede server processing.

Http status return code

Code Description
400 (incorrect request) the server does not understand the request syntax.
401 (unauthorized) requests require authentication. The server may return this response for webpages that require logon.
403 (Forbidden) The server rejects the request.
404 (not found) The server cannot find the requested webpage.
405 (method disabled) disable the method specified in the request.
406 (unacceptable) unable to respond to the requested webpage using the requested content features.
407 (proxy authorization required) this status code is similar to 401 (unauthorized), but the specified requester should authorize the use of proxy.
408 (request timeout) timeout occurred when the server waited for the request.
409 conflict occurs when the server completes the request. The server must contain conflict information in the response.
410 (Deleted) If the requested resource has been permanently deleted, the server returns this response.
The 411 (valid length required) server does not accept requests that do not contain valid Content Length header fields.
412 (not meeting the prerequisites) the server does not meet one of the prerequisites set by the requester in the request.
413 (the Request Entity is too large) The server cannot process the request because the request entity is too large and exceeds the server's processing capability.
414 (the requested URI is too long) The request URI (usually the URL) is too long and cannot be processed by the server.
415 (unsupported media type) The request format is not supported by the request page.
416 (the request range does not meet the requirements) if the page cannot provide the request range, the server returns this status code.
417 (not meeting expectations) the server does not meet the "expectation" request header field requirements.

Http status return code5xx (server error)
These status codes indicate an internal error occurred when the server attempted to process the request. These errors may be server errors rather than request errors.

Http status return code

Code Description
500 (internal server error) The server encounters an error and cannot complete the request.
501 (not implemented) the server does not have the function to complete the request. For example, this Code may be returned when the server cannot identify the request method.
The 502 (error gateway) server acts as a gateway or proxy and receives an invalid response from the upstream server.
503 (Service unavailable) servers are currently unavailable (due to overload or downtime maintenance ). Generally, this is only a temporary status.
504 (gateway timeout) The server acts as a gateway or proxy, but does not receive a request from the upstream server in time.
505 (HTTP Version Not Supported) the server does not support the HTTP protocol version used in the request.

Some common Http status return codeIs:

200-the server returns the webpage successfully
404-the requested webpage does not exist
503-service unavailable

Original article: http://blog.sina.com.cn/s/blog_4ae187490100x9u7.html