| message response |
|---|
| 100 | Continue
(Continue) | The client should continue to send requests. This temporary response is used to inform the client that part of its request has been received by the server and has not yet been denied. The client should continue sending the rest of the request, or ignore the response if the request has been completed. The server must send a final response to the client after the request is completed. | HTTP/1.1 is available |
| 101 | Switching Protocol
(Switching protocol) | The server has understood the client's request and will notify the client through the Upgrade header to use a different protocol to complete the request. After sending the last blank line of this response, the server will switch to the protocols defined in the Upgrade header.: Similar measures should be taken only when it is more beneficial to switch to a new protocol. For example, switching to a new version of HTTP has an advantage over an older version, or switching to a real-time and synchronized protocol to deliver resources that take advantage of such characteristics. | HTTP/1.1 is available |
| success response |
|---|
| 200 | OK
(Success) | The request was successful. The meaning of success varies depending on the method used for the request.GET: The resource has been extracted and returned to the client as the response body. HEAD: The entity header has been returned to the client as a response header POST: After the server processes the data from the client, appropriate resources are sent back to the client as a response body. TRACE: The server receives the request message and returns it to the client as a response body.
PUT, DELETE, and OPTIONS methods never return a 200 status code. | HTTP/0.9 available |
| 201 | Created
(Created) | The request was successful and a new resource has been created based on the needs of the request. This is usually the response code obtained by the PUT method. | HTTP/0.9 available |
| 202 | Accepted
(Created) | The server accepted the request but has not yet processed it. Just as it may be denied, the request may or may not be executed in the end. In the case of asynchronous operations, there is no more convenient way to send this status code.: The purpose of a response that returns a 202 status code is to allow the server to accept requests from other processes (such as a batch-based operation that is executed only once a day) without having to keep the client connected to the server until the batch operation is completed. A response that accepts the request for processing and returns a 202 status code should contain some information in the returned entity indicating the current status of the process, as well as a pointer to a process status monitor or status prediction, so that the user can estimate whether the operation has been completed. | HTTP/0.9 available |
| 203 | Non-Authoritative Information
(Unauthorized information) | The server has successfully processed the request, but the entity header meta information returned is not a determined collection valid on the original server, but a copy from a local or third party. If this is not the case, a 200 status code is the most appropriate. | HTTP/0.9 and 1.1 |
| 204 | No Content
(No content) | The response has no response content, only a response header, which may also be useful. The user agent can update the cache information of the corresponding resource based on the new response header. | HTTP/0.9 available |
| 205 | Reset Content
(Reset content) | Tell the user agent to reset the document view of the window that sent the request. | HTTP/1.1 is available |
| 206 | Partial Content
(Part of the content) | This status code is used when the client downloads a file segment by using the range header field | HTTP/1.1 is available |
| redirected |
|---|
| 300 | Multiple Choice
(Multiple options) | There are multiple possible responses to the request, and the user agent or user must select one of them. The server has no standards to follow to replace the user in making choices. | HTTP/1.0 and later |
| 301 | Moved Permanently
(permanent move) | This status code indicates that the requested URI resource path has changed, and the new URL will be found in the Location: header field of the response. | HTTP/0.9 available |
| 302 | Found
(Temporary movement) | This status code indicates that the requested URI resource path has temporarily changed and may continue to change. Therefore, the client must continue to use the URI for future visits. The new URL will be found in the Location: header field of the response. | HTTP/0.9 available |
| 303 | See Other
(View other locations) | The server sends the response to direct the client to access another URI using the GET method. | HTTP/0.9 and 1.1 |
| 304 | Not Modified
(Unmodified) | Tells the client that the requested content has not changed since the last visit. The client can retrieve the resource directly from the browser cache. | HTTP/0.9 available |
| 305 | Use Proxy
(Use of Agents) | The requested resource must be accessed through a proxy. Due to security reasons, this status code is not widely supported. | HTTP/1.1 is available |
| 306 | unused
(unused) | This status code is no longer in use; it was used in older versions of the HTTP 1.1 specification. | HTTP/1.1 is available |
| 307 | Temporary Redirect
(Temporary redirect) | The server sends this response to guide the client to use the same method to access another URI to obtain the resource it wants. The new URL will be found in the Location: header field of the response. It has the same semantics as the 302 status code, and the same method must be used for both accesses (GET POST). | HTTP/1.1 is available |
| 308 | Permanent Redirect
(Permanently redirected) | The requested resource will be permanently located on another URI. The new URL will be found in the Location: header field of the response. It has the same semantics as the 301 status code, and the same method must be used for both accesses (GET POST). | HTTPbis
(Test Draft) |
| client error |
|---|
| 400 | Bad Request
(Wrong request) | The server cannot read the request properly due to an incorrect syntax. | HTTP/0.9 available |
| 401 | Unauthorized
(Unauthorized) | Authentication is required to obtain the requested content, similar to a 403 error. The difference is that after a. 401 error, as long as you enter the account password correctly, the verification will pass. | HTTP/0.9 available |
| 402 | Payment Required
(Payment required) | The status code is reserved for future use. This code was originally created for digital payment systems, but it has not been put into use until now. | HTTP/0.9 and 1.1 |
| 403 | Forbidden
(Access prohibited) | The client does not have the right to access the requested content, and the server denies the request. | HTTP/0.9 available |
| 404 | Not Found
(not found) | The server cannot find the requested resource. Because this happens frequently, this status code is very common when surfing the Internet. | HTTP/0.9 available |
| 405 | Method Not Allowed
(This method is not allowed) | The method used in this request is prohibited by the server. RFC2616 stipulates that GET and HEAD methods cannot be prohibited. | HTTP/1.1 is available |
| 406 | Not Acceptable
(Unacceptable) | After server-driven content negotiation, no suitable content was found and sent back to the client. | HTTP/1.1 is available |
| 407 | Proxy Authentication Required
(Require agent authentication) | Similar to status code 401, but requires a proxy to verify it. | HTTP/1.1 is available |
| 408 | Request Timeout
(Request timed out) | The client did not complete sending a request within the time the server was prepared to wait. This means that the server will cut off the connection with the client. This response is more common in other browsers, such as Chrome and IE9, in order to speed up browsing using the HTTP pre-connect mechanism. Also note that some servers directly disconnect the connection without sending such a response. | HTTP/1.1 is available |
| 409 | Conflict
(Conflict) | The request conflicts with the current state of the server. | HTTP/1.1 is available |
| 410 | Gone
(expired) | The requested resource has been deleted. | HTTP/1.1 is available |
| 411 | Length Required
(Requires content length header) | Because the server required the Content-Length header field in this request, but the client did not send it. Therefore, the server refused the request. | HTTP/1.1 is available |
| 412 | Precondition Failed
(Preprocessing failed) | The server failed to meet the prerequisites set by the client in the request header field when obtaining resources. | HTTP/1.1 is available |
| 413 | Request Entity Too Large
(Request entity is too long) | The request entity size exceeds the maximum limit set by the server, and the server may close the HTTP link and return the Retry-After header field. | HTTP/1.1 is available |
| 414 | Request-URI Too Long
(Request URL is too long) | The client request contains a URI address that is too long for the server to process. | HTTP/1.1 is available |
| 415 | Unsupported Media Type
(Media type not supported) | The server does not support the media type requested by the client and therefore denies the request. | HTTP/1.1 is available |
| 416 | Requested Range Not Satisfiable
(The scope of the request is not satisfactory) | The Range header field included in the request cannot be satisfied, usually because the range of numbers in the Range exceeds the size of the requested resource. | HTTP/1.1 is available |
| 417 | Expectation Failed
(Expected results fail) | The expected content specified in the request header Expect cannot be satisfied by the server. | HTTP/1.1 is available |
| Server side error |
|---|
| 500 | Internal Server Error
(Internal server error) | The server encountered an unknown and unresolvable problem. | HTTP/0.9 available |
| 501 | Implemented
(Not realized) | The server does not support the methods used in this request, such as POST and PUT. Only GET and HEAD are the methods that the server must implement in the RFC2616 specification. | HTTP/0.9 available |
| 502 | Bad Gateway
(Gateway error) | The server acted as a gateway and received an invalid HTTP response from an upstream server. | HTTP/0.9 available |
| 503 | Service Unavailable
(Service not available) | Due to temporary server maintenance or overload, the server is currently unable to process requests. This situation is temporary and will recover after a period of time. If the delay time can be predicted, the response can include a Retry-After: header to indicate the delay time. If this Retry-After: information is not given, then the client should process it as a 500 response. Also, in this case, a friendly page explaining the problem with the server should be returned, and cache-related HTTP header information should also be included, because usually this error tells that the page should not be cached by the client. | HTTP/0.9 available |
| 504 | Gateway Timeout
(Gateway timeout) | The server acts as a gateway and cannot get timely responses from upstream servers and return them to the client. | HTTP/1.1 is available |
| 505 | HTTP Version Not Supported
(HTTP Version is not supported) | The server does not support the version of the HTTP protocol used in the HTTP request sent by the client. | HTTP/1.1 is available |
English
简体中文
繁体中文
