Status Codes¶
Table 1 describes the status codes.
Status Code | Message | Description |
|---|---|---|
100 | Continue | The client should continue with its request. This interim response is used to inform the client that the initial part of the requests has been received and not rejected by the server. |
101 | Switching Protocols | The protocol should be switched. The protocol can only be switched to a more advanced protocol. For example, a new HTTP protocol. |
200 | OK | The request has succeeded. |
201 | Created | The request has been fulfilled, resulting in the creation of a new resource. |
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 | No Content | The server has successfully processed the request, but does not return any content. 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 the GET request. |
300 | Multiple Choices | There are multiple options for the location of the requested resource. The response contains a list of resource characteristics and addresses from which a user terminal (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 response to the request can be found under a different URI, and should be retrieved using a GET or POST method. |
304 | Not Modified | The requested resource has not been modified. When the server returns this status code, it does not return any resources. |
305 | Use Proxy | The requested resource must be accessed through a proxy. |
306 | Unused | This HTTP status code is no longer used. |
400 | Bad Request | The request is invalid. The client should not repeat the request without modifications. |
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 rejected. 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 | Not Found | The requested resource cannot be found. The client should not repeat the request without modifications. |
405 | Method Not Allowed | The method specified in the request is not supported by the requested resource. The client should not repeat the request without modifications. |
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 indicates that the client must authenticate itself with the proxy first. |
408 | Request Timeout | 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 later. |
409 | Conflict | The request cannot be processed 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 cannot 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 server refuses to process a request because the request entity is too large. 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 field. |
414 | Request-URI Too Long | 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 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 | Internal Server Error | The server is able to receive the request but unable to understand the request. |
501 | Not Implemented | The server does not support the function required to fulfill the request. |
502 | Bad Gateway | The server acting as a gateway or proxy receives an invalid response from a remote server. |
503 | Service Unavailable | The requested service is invalid. The client should not repeat the request without modifications. |
504 | Server Timeout | 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. |