HTTP Return Code Summary

The meaning of the HTTP protocol status code is mainly divided into five categories, which are generally:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1XX reserved
2XX indicates that the request was successfully received by
3XX request further refinement of requests for completion of customer requests
4XX Customer Error
5XX Server Error

Continue
Indicates that the client should continue the request. Loopback is used to notify the client that this request has been received and is not rejected by the server.
The client should continue to send the remaining request data, or the request has been completed, or the loopback data is ignored. The server must send
The final loopback is after the request.

101 Switching protocols
The server changes the current connection application protocol according to the customer service request, through the upgrade header information. The server will immediately change the protocol based on the upgrade header
At the end of the 101 send-back with a blank line.

Successful
=================================
OK
Indicates that the client's request has been successfully received, resolved, accepted.

201 Created
The request is complete and a new return resource is created. The resource that is created may be a URI resource, usually a URI resource specified in the location header. Loopback should contain one entity data
It also contains resource attributes and location to select the appropriate method through the user or user agent. The Entity Data format specifies the Content-type head by the coal type. The first server
The specified resource must be created before the 201 status code is returned. If the behavior is not executed immediately, the server should return 202.

202 Accepted
The request has been accepted for processing. But the processing did not complete. The request might or may not have been followed because the processing might have been rejected during the actual execution.

203 non-authoritative Information

204 No Content
The server has accepted the request and does not need to return the Entity data, and may need to return the update information. The loopback may contain new or updated information that is rendered by entity-headers.

205 Reset Content
The server has accepted the request and the user agent should reset the document view.

206 Partial Content
The server has accepted the part of the request GET request resource. The request must contain a range header information to indicate that the fetch scope may have to contain the If-range header information to form the request condition.

Redirection
==================================
Multiple Choices
The request resource conforms to any one of the rendering methods.

301 Moved Permanently
The requested resource has been assigned a new URI.

302 Found
A temporary file that requests resources through different URIs.
303 See other

304 Not Modified
If the client has completed a conditional request and the request is allowed, but the document does not change, the server should return a 304 status code. 304
The status code must not contain the information body, which usually ends with the first empty line after a header field.

305 Use Proxy
The requested resource must be accessed through the proxy (specified by the Location field). The location resource gives the URI of the proxy.

306 Unused

307 Temporary Redirect

Client Error
=====================
Request
The server cannot understand the request information because of the incorrect syntax.

401 Unauthorized
If the request requires user authentication. The loopback should contain a Www-authenticate header field that indicates the permission to request the resource.

402 Payment Required
Reserved status code

403 Forbidden
The server accepts the request, but is denied processing.

404 Not Found
The server has found any resources that match Request-uri.

405 Menthod not allowed
Request-line The requested method is not allowed through the specified URI.

406 Not acceptable

407 Proxy Authentication Required

408 Reqeust Timeout
The customer service side did not submit any requests within the server waiting time for processing.

409 Conflict

410 Gone

411 Length Required
The server refused to accept the request without defining the Content-length field.

412 Precondition Failed

413 Request Entity Too Large
The server refuses to process the request because the request data exceeds the scope that the server can handle. The server may close the current connection to prevent the client from continuing the request.

414 Request-uri Too Long
Server denial of service current request because the length of the URI exceeds the resolution range of the server.

415 Unsupported Media Type
The server denies the service the current request because the request data format is not supported by the requested resource.

416 Request Range Not satisfialbe

417 Expectation Failed

Server Error
===================================
Internal Server Error
Server encounters an exception that prevents execution of the current request

501 Not implemented
The server does not have a corresponding execution action to complete the current request.

502 Bad Gateway

503 Service Unavailable
The server cannot process the current request because of a temporary file overload.

504 Gateway Timeout

505 Http Version not supported