Status Codes
Table 1 describes HTTP response status codes.
Status Code |
Message |
Description |
---|---|---|
100 |
Continue |
Continue sending requests. This temporary response is used to inform the client that some requests have been received and not rejected by the server. |
101 |
Switching Protocols |
Switch the protocol. The target protocol must be more advanced than the original one. For example, the protocol in use is switched to a later version of HTTP. |
201 |
Created |
The request for creating resources has been fulfilled. |
202 |
Accepted |
The request has been accepted for processing, but the processing has not been completed. |
203 |
Non-Authoritative Information |
The request was successful but the response has been modified by a transforming proxy. |
204 |
No Content |
The request has been fulfilled, but the HTTP response does not contain a response body. The status code is returned in response to an HTTP OPTIONS request. |
205 |
Reset Content |
The server has fulfilled the request and requires the client to reset the content. |
206 |
Partial Content |
The server has fulfilled a range GET request. |
300 |
Multiple Choices |
There are multiple options for the requested resource. The response contains a list of resource characteristics and addresses from which the user or user agent (such as a browser) can choose the most appropriate one. |
301 |
Moved Permanently |
The requested resource has been assigned with a new permanent URI. This new URI is contained in the response. |
302 |
Found |
The requested resource resides temporarily under a different URI. |
303 |
See Other |
The server is redirecting the client to a different address. The client should use a GET or POST method to obtain the resource. |
304 |
Not Modified |
The requested resource has not been modified. When the server returns this status code, no resource is returned. |
305 |
Use Proxy |
The requested resource is available only through a proxy. |
306 |
Unused |
This HTTP status code is no longer used. |
400 |
Bad Request |
Invalid request. The client should not repeat this request without modification. |
401 |
Unauthorized |
The authentication information provided by the client is incorrect or invalid. |
402 |
Payment Required |
This status code is reserved for future use. |
403 |
Forbidden |
The request has been rejected. The server received and understood the request but refused to fulfill it, because the request is set to deny access. The client should not repeat this request without modification. |
404 |
Not Found |
The requested resource could not be found. The client should not repeat this request without modification. |
405 |
Method Not Allowed |
The method specified in the request is not allowed for the requested resource. The client should not repeat this request without modification. |
406 |
Not Acceptable |
The server cannot implement the request based on the content characteristics of the request. |
407 |
Proxy Authentication Required |
This status code is similar to 401, but the client must be authenticated using a proxy. |
408 |
Request Time-out |
The client does not produce a request within the time that the server was prepared to wait. The client may repeat the request without modifications at any time later. |
409 |
Conflict |
The request cannot be processed due to a conflict. The resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
410 |
Gone |
The requested resource is no longer available. The requested resource has been deleted permanently. |
411 |
Length Required |
The server fails to process the request which does not contain the Content-Length header field. |
412 |
Precondition Failed |
The server does not meet one of the requirements that the requester puts on the request. |
413 |
Request Entity Too Large |
The request is larger than that the server can process. The server may close the connection to prevent the client from continuously sending the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field. |
414 |
Request-URI Too Large |
The Request-URI is too long for the server to process. |
415 |
Unsupported Media Type |
The server cannot process the media format in the request. |
416 |
Requested Range Not Satisfiable |
The requested range is invalid. |
417 |
Expectation Failed |
The server fails to meet the requirements of the Expect request header field. |
422 |
Unprocessable Entity |
The request is well-formed but is unable to be processed due to semantic errors. |
429 |
Too Many Requests |
The client sends too many requests to the server within a given time, exceeding the client's access frequency limit or beyond the server's processing capability. In this case, the client should retry after the time period specified in the Retry-After response header. |
500 |
Internal Server Error |
The server is able to receive the request but unable to understand it. |
501 |
Not Implemented |
The server does not support the function required to fulfill the request. |
502 |
Bad Gateway |
The server was acting as a gateway or proxy and received an invalid request from a remote server. |
503 |
Service Unavailable |
The requested service is invalid. The client should not repeat this request without modification. |
504 |
Server Timeout |
The request cannot be fulfilled within a given amount of time. The response will reach the client only if the request carries a timeout parameter. |
505 |
HTTP Version Not Supported |
The server does not support the HTTP protocol version used in the request. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.