A list of common HTTP status codes for production environments

When the server responds to the client, it responds with the corresponding status code, and different status codes have different meanings.

1XX: Information class

2XX: Success Class

3XX: Redirect Class

4XX: Client Error class

5XX: Service-side Error class

200-OK, the server successfully returned to the Web page

-standard response for successful HTTP requests.

301-moved permanently (permanent jump), the requested page has been permanently redirected to the new location.

-This and all of the future requests should is directed to the given.

403-forbidden (no access), the server rejects the request

-Forbidden request (matches a deny filter) = HTTP 403

-the request was a legal request and the server is refusing to respond to it.

404-not Found, the server could not find the requested page.

-The requested resource could is not being found but may is available again in the future.

500-internal Server error (internal server errors)

-Internal Error in Haproxy = HTTP 500

-A generic error message, given when no more specific message is suitable.

502-bad Gateway (Bad Gateway), typically when the gateway server requests the backend service, the backend service does not return the results correctly as the HTTP protocol.

-the server returned an invalid or incomplete response = HTTP 502

-The server was acting as a gateway or proxy and received a invalid response from the upstream server.

503-service unavailable (service is not currently available), may be due to overloading or downtime maintenance.

-No server is available to handle the request + = 503

-The server is currently unavailable (because it was overloaded or down for maintenance).

504-gateway Timeout (gateway timeout), typically when a gateway server requests a backend service, the backend service does not complete the service in a specific time period.

-The server failed to reply in time + = HTTP 504

-The server was acting as a gateway or proxy and do not receive a timely response from the upstream server.

More:

Some common HTTP status codes are:

200– server successfully returned to Web page

404– The requested page does not exist

503– Service Not available

Common HTTP status Code Daquan

1XX (Temporary response)

A status code that represents a temporary response and requires the requestor to continue the operation.

Code description

HTTP status Code 100 (continued) The requestor should continue to make the request. The server returns this code to indicate that the first part of the request was received and is waiting for the remainder.

HTTP Status Code 101 (switching protocol) The requestor has asked the server to switch protocols and the server has confirmed and is ready to switch.

2XX (Success)

Represents the status code that successfully processed the request.

Code description

HTTP status Code 200 (success) The server has successfully processed the request. Typically, this indicates that the server provided the requested Web page.

HTTP status Code 201 (created) The request was successful and the server created a new resource.

HTTP Status Code 202 (accepted) the server has accepted the request but has not yet processed it.

HTTP status Code 203 (non-authoritative information) the server has successfully processed the request, but the information returned may be from another source.

HTTP status Code 204 (no content) the server successfully processed the request, but did not return any content.

HTTP status Code 205 (reset content) the server successfully processed the request, but did not return any content.

HTTP Status Code 206 (partial) The server successfully processed a partial GET request.

3XX (redirected)

Indicates that further action is required to complete the request. Typically, these status codes are used for redirection.

Code description

HTTP status Code 300 (multiple choices) for requests, the server can perform a variety of operations. The server can select an action based on the requestor (user agent) or provide a list of actions for the requestor to select.

HTTP status Code 301 (permanently moved) The requested Web page has been permanently moved to a new location. When the server returns this response (a response to a GET or HEAD request), the requestor is automatically forwarded to the new location.

HTTP Status Code 302 (temporary move) The server is currently responding to requests from different locations, but the requestor should continue to use the original location for future requests.

HTTP Status Code 303 (view other locations) The server returns this code when the requestor should use a separate GET request for the different locations to retrieve the response.

HTTP status Code 304 (not modified) The requested webpage has not been modified since the last request. When the server returns this response, the Web page content is not returned.

HTTP status Code 305 (using proxies) the requestor can only use the proxy to access the requested Web page. If the server returns this response, it also indicates that the requestor should use the proxy.

HTTP status Code 307 (temporary redirection) The server is currently responding to requests from a Web page in a different location, but the requestor should continue to use the original location for future requests.

4xx (Request error)

These status codes indicate a possible error in the request and hinder the processing of the server.

Code description

HTTP Status Code 400 (Error request) The server does not understand the syntax of the request.

HTTP status Code 401 (unauthorized) request authentication required. The server may return this response for pages that need to log on.

HTTP status Code 403 (forbidden) The server rejects the request.

HTTP status code 404 (not found) The requested Web page was not found by the server.

HTTP Status Code 405 (method disabled) Disables the method specified in the request.

The HTTP status Code 406 (not accepted) cannot use the requested content attribute to respond to the requested Web page.

HTTP status Code 407 (requires proxy authorization) This status code is similar to 401 (unauthorized), but specifies that the requestor should authorize the use of the proxy.

HTTP status Code 408 (Request timed out) A timeout occurred while the server was waiting for a request.

HTTP status Code 409 (conflict) The server has a conflict when it finishes the request. The server must include information about the conflict in the response.

HTTP status Code 410 (deleted) The server returns this response if the requested resource has been permanently deleted.

HTTP status Code 411 (requires valid length) The server does not accept requests that do not contain a valid Content-Length header field.

HTTP status Code 412 (Prerequisites not met) the server does not meet one of the prerequisites set by the requestor in the request.

HTTP status Code 413 (Request entity too Large) The server cannot process the request because the request entity is too large to exceed the processing power of the server.

HTTP status Code 414 (the requested URI is too long) The requested URI (usually a URL) is too long for the server to process.

HTTP status Code 415 (Unsupported media type) The requested format is not supported by the requested page.

HTTP status Code 416 (request scope does not meet requirements) if the page cannot provide the requested scope, the server returns this status code.

HTTP status Code 417 (unmet expectations) the server did not meet the requirements for the "expected" Request header field.

5XX (server error)

These status codes indicate that the server has an internal error while trying to process the request. These errors may be the error of the server itself, not the request.

Code description

HTTP status Code 500 (server internal error) the server encountered an error and could not complete the request.

HTTP status Code 501 (not yet implemented) the server does not have the ability to complete the request. For example, this code may be returned when the server does not recognize the request method.

HTTP Status Code 502 (Error Gateway) The server receives an invalid response from the upstream server as a gateway or proxy.

HTTP Status Code 503 (Service Unavailable) the server is not currently available (due to overloading or downtime maintenance). Typically, this is only a temporary state.

HTTP status Code 504 (Gateway timed out) The server acts as a gateway or proxy, but does not receive requests from the upstream server in a timely manner.

HTTP status Code 505 (HTTP version not supported) the HTTP protocol version used in the request is not supported by the server.

Several interesting graphs to help you understand the HTTP status code

HTTP status code (figure I):

650) this.width=650; "Src=" http://mmbiz.qpic.cn/mmbiz_jpg/ vqlbvfl5jn2m1xc6zjeiczjcwhy5pjweixyefuudjb5aahyricwics0kgcoa68qvbeltaz5vcv7tsr16dx7oporwq/640?wx_fmt=jpeg& Tp=webp&wxfrom=5&wx_lazy=1 "style=" Margin:0px;padding:0px;height:auto;width:auto; "alt=" 640?wx_fmt=jpeg &tp=webp&wxfrom=5&wx_lazy "/>

Comments:

• 301 -Move permanently. The requested resource has been permanently moved to the location;

• 302 -The requested resource is now temporarily responding to requests from different URIs;

• 305 -Use a proxy. The requested resource must be accessed through the specified proxy;

• 307 -Temporary jump. The requested resource responds to the request on a temporary basis from a different URL;

• - -Error requests;

• 402 -Payment is required. This status code is reserved for possible future requirements and is used in some digital currencies or micro-payments;

• 403 -No access. The server has understood the request, but refuses to execute it;

• 404 -The object cannot be found. The request fails and the resource does not exist;

• 406 -Unacceptable. The content attribute of the requested resource could not satisfy the condition in the request header, so the response entity could not be generated;

HTTP status code (Figure II):

650) this.width=650; "Src=" http://mmbiz.qpic.cn/mmbiz_jpg/ Vqlbvfl5jn2m1xc6zjeiczjcwhy5pjwei5xm1vq3nibgjkyhvzk55ickpucibqtvgbmkgozth4yzv6e15gmhpvdwpa/640?wx_fmt=jpeg &tp=webp&wxfrom=5&wx_lazy=1 "style=" Margin:0px;padding:0px;height:auto;width:auto; "alt=" 640?wx_fmt= Jpeg&tp=webp&wxfrom=5&wx_lazy "/>

Comments:

• 408 -Request timed out;

• 409 -conflict. The request cannot be completed because there is a conflict between the current state of the requested resource and the request;

• 410 -Lost. The requested resource is no longer available on the server, and there is no known forwarding address;

• 413 -The response entity is too large. The server refuses to process the current request, exceeding the maximum value that the server can handle and allow.

• 417 -expected failure. The expected content specified in the request header Expect could not be satisfied by the server;

• 418 -I am a teapot. Hypertext Coffee Pot Control Protocol, but is not implemented by the actual HTTP server;

• 420 -Method failed.

• 422 -entities that are not processed. The request is well-formed, but cannot respond due to a semantic error;

• - -Server Internal error. The server encountered an unexpected condition that caused it to not be able to complete the processing of the request;

This article is from the "Old White blog" blog, please be sure to keep this source http://laobaiv1.blog.51cto.com/2893832/1981258

List of HTTP status codes common to production environments