HTTP Status Code meaning

HTTP Status Code meaning 1XX

** Continue: Informs the client that the operation can continue　　

 * 101 Switching protocols: When a client needs to make a communication protocol switch, the server-side response is used in conjunction with the upgrade header　　

2XX

*** Ok: The server correctly responds to the request and returns the status code if it does not match the other 2XX status code 　

*** 201 Created: Client request to create a new resource succeeded

* * 202 Accepted: Indicates that the server has accepted the request but has not processed it, primarily for asynchronous operations　

* 203 non-authoritative Information: Data that represents the service-side response is not aware of the accuracy of the response, possibly because the data originated from a third party

*** 204 No content: The server refuses to give Put,post or delete response content when using this status code, or a GET request when the resource exists, but the content is empty

* 205 reset Content: Similar to 204, but resets the data in the form

*** 206 Partial Content: Response partial data from the client using range to request a resource

3XX

 * multple cholces: The requested resource server has multiple, but it does not know the response to what the expression, if there is a default representation using the location response header　　

** 301 Moved permantly: The server wants the client to access another URL and wants the client to remember to place the URL in the location response header

x 302 Found

*** 303 See other: Indicates that the request has been processed, but not directly in response to the resource representation, but instead returns the URL of a response file that the client can access or not access

*** 304 Not Modified: No response entity, indicating that the resource has not been modified

* 305 Use proxy: You want the client to resend the request, which needs to be sent over the HTTP proxy, which contains the URI of the proxy　　

*** 307 Temporary Redirect: The request was not processed because the requested resource is not local and at a different URI requires the client to re-request

4XX

 *** bad Request: Generic client-side error, also used to indicate that the submitted data is malformed and cannot be processed by the server

 *** 401 unauthorized:http The response of the resource when the form or Digest authentication fails.

x 402 Payment Required: For the payment system, which indicates that the client needs to be paid before allowing access to resources, but is not currently used

** 403 Forbidden: The resource requires HTTP authentication to allow access, or because other restrictions do not allow access　　

 *** 404 Not Found: The server could not convert the URI into a resource

** 405 Method Not allowed: The resource does not support the HTTP methods, and the server response is using the Allow header to list which methods are supported by the support

  ** 406 Not acceptable: The server does not support too many accept-request requests from the client, and the server can return a first response

* 407 Proxy Authentication The response sent by the Required:http proxies, indicating that HTTP authentication is required, or that the authentication data provided is incorrect

* 408 Request Timeout: The server closes the link when the client does not send data after the connection has been established, or if it does not send a blank line representing the end of the response

*** 409 Conflict: Request causes server resources to be in an inconsistent state

** 410 Gone: Similar to 404, but in more detail, indicates that the resource existed before, but now no longer exists, and does not know the current URI of the resource

 * 411 Length Required: The server needs to know the content-length data, but the client does not provide

* 412 Precondition Failed: The condition of processing the request is not satisfied, such as if-unmodified-since tell the time check failed

* 413 Request entity Too Large: The Entity data sent by the client is too large for the server to process

* 414 Request-uri Too Long: The server considers the URI too long

** 415 Unsupported Media Type: The server cannot specify a format response to the client

* 416 Request Range not satisdiable: The server cannot satisfy a range of resources, such as a resource with only 100 bytes, but range is 1-200

* 417 Expectation Failed: In contrast to 100, indicates a client's expected failure

+ 428 Precondition Required: lack of preconditions

+ 429 Too Many requests: too many client requests

+ 431 Request Header fields Too Large: Too many requests header contents

5XXX

* 　 * Internal Server error: Server-wide errors typically encountered when processing resources by the server

* 501 not implemented: HTTP features not supported by the server, such as sending a copy request to the client

* 502 Bad Gateway: A problem with the agent or a problem between the agent and the upstream server　　　

 ** 503 Service unavailable:http server is OK, but the Web server does not work, possibly due to the excessive number of requests cannot be processed all

* 504 Gateway Timeout: The proxy server cannot connect to the upstream server

* 505 HTTP version not supported: The server does not support HTTP versions of clients, such as sending http/1.1 to an HTTP 1.0 server

  + 511 network authentication Required: Clients require authentication to access Web resources, such as Wi-Fi hotspots

——————————————————————————

Indicates a high usage rate

* * indicates low usage rate

* Indicates low usage rate

X means not recommended, or not used

+ indicates that the status code is not defined in RFC 26161, but is defined in RFC 6585, which updates RFC 2616

RFC 6585 was released in April 2012 and currently has no server support

Thank you: CSDN Dragon fruit Share this knowledge note. (￣︶￣)/

HTTP Status Code meaning