Status Codes¶
Table 1 describes status codes.
Status Code | Message Title | Description |
|---|---|---|
100 | Continue | The client continues sending the request. The server has received the initial part of the request and the client should continue sending the remaining part. |
101 | Switching Protocols | The protocol should be switched and can only be switched to a more advanced protocol. For example, the current HTTP protocol is switched to a later version. |
201 | Created | The request for creating a resource has been fulfilled. |
202 | Accepted | The request has been accepted, but the processing has not been completed. |
203 | Non-Authoritative Information | The server successfully processed the request, but is returning information that may be from another source. |
204 | NoContent | The server has successfully processed the request, but is not returning any response body. The status code is returned in response to an HTTP OPTIONS request. |
205 | Reset Content | The server has fulfilled the request, but the requester is required to reset the content. |
206 | Partial Content | The server has successfully processed a part of a 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 a new permanent URI, and the new URI is contained in the response. |
302 | Found | The requested resource resides temporarily under a different URI. |
303 | See Other | The response to the request can be found under a different URI. It should be retrieved using a GET or POST method. |
304 | Not Modified | The requested resource has not been modified. If the server returns this status code, no resource will be returned. |
305 | Use Proxy | The requested resource must be accessed through a proxy. |
306 | Unused | The HTTP status code is no longer used. |
400 | BadRequest | The request is invalid. The client should modify the request instead of re-initiating it. |
401 | Unauthorized | The authorization information provided by the client is incorrect or invalid. |
402 | Payment Required | This status code is reserved for future use. |
403 | Forbidden | The request is denied. The server has received the request and understood it, but the server is refusing to respond to it. The client should not repeat the request without modifications. |
404 | NotFound | The requested resource could not be found. The client should modify the request instead of re-initiating it. |
405 | MethodNotAllowed | The method specified in the request is not supported for the requested resource. The client should modify the request instead of re-initiating it. |
406 | Not Acceptable | The server cannot fulfill 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 first authenticate itself with the proxy. |
408 | Request Time-out | The server times out when waiting for the request. The client may repeat the request without modifications at any later time. |
409 | Conflict | The request could not be completed due to a conflict. The resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request. |
410 | Gone | The requested resource could not be found. The requested resource has been deleted permanently. |
411 | Length Required | The server refuses to process the request without a defined Content-Length. |
412 | Precondition Failed | The server does not meet one of the preconditions that the requester puts on the request. |
413 | Request Entity Too Large | The request is larger than the server is willing or able to process. The server may disable the connection to prevent the client from sending requests consecutively. 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 is unable to 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 | UnprocessableEntity | The request is well-formed but is unable to be processed due to semantic errors. |
429 | TooManyRequests | The client sends excessive requests to the server within a given time (exceeding the limit on the access frequency of the client), or the server receives excessive requests within a given time (beyond its processing capability). In this case, the client should repeat requests after the time specified in the Retry-After header of the response expires. |
500 | InternalServerError | The server is able to receive the request, but it could not understand the request. |
501 | Not Implemented | The server does not support the functionality required to fulfill the request. |
502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
503 | ServiceUnavailable | The requested service is invalid. The client should modify the request instead of re-initiating it. |
504 | ServerTimeout | The request cannot be fulfilled within a given time. This status code is returned to the client only when the Timeout parameter is specified in the request. |
505 | HTTP Version not supported | The server does not support the HTTP protocol version used in the request. |