Status Codes¶
An HTTP status code consists of three digits, which is classified into five categories: 1xx: related information; 2xx: operation successful; 3xx: redirection; 4xx: client error; 5xx: server error.
The following table lists the common status codes.
Status Code | Message | Description |
|---|---|---|
100 | Continue | The client should proceed with the request. This interim response is used to inform the client that part of the request has been received and has not yet been rejected by the server. |
101 | Switching Protocols | The server is switching to a new protocol. The target protocol must be more advanced than the original one. For example, a later version of HTTPS is used. |
200 | OK | The server has successfully processed the request. |
201 | Created | The request has been fulfilled and resulted in a new resource being created. |
202 | Accepted | The request has been accepted, but the processing has not been completed. |
203 | Non-Authoritative Information | The request has been fulfilled. |
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 and requires the client to reset the content. |
206 | Partial Content | The server has fulfilled the partial GET request for the resource. |
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 the user or user agent (such as a browser) can choose the most appropriate one. |
301 | Moved Permanently | This and all future requests have been permanently moved to the given URI indicated in this response. |
302 | Found | The requested resource has been temporarily moved. |
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, no resource is returned. |
305 | Use Proxy | The requested resource is available only through a proxy. |
306 | Unused | The HTTP status code is no longer used. |
400 | Bad Request | Invalid request. Modify the request directly and do not attempt to retry it. |
401 | Unauthorized | The authorization information provided by the client is incorrect or invalid. |
402 | Payment Required | Reserved request. |
403 | Forbidden | The request is rejected. The server has received and understood the request, but refused to respond to it. Modify the request directly and do not attempt to retry it. |
404 | Not Found | The requested resource does not exist. Modify the request directly and do not attempt to retry it. |
405 | Method Not Allowed | The request contains a method that is not supported by the resource. Modify the request directly and do not attempt to retry it. |
406 | Not Acceptable | The server could not fulfil the request based on the 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 Timeout | The request timed out. The client can resubmit the request at any time without making any changes. |
409 | Conflict | The server encountered a conflict fulfilling the request. This status code indicates that the resource the client is attempting to create already exists, or that the update operation requested cannot be completed due to a conflict. |
410 | Gone | The resource requested by the client no longer exists. This status code indicates that the requested resource has been permanently deleted. |
411 | Length Required | The server refuses to process the request without a defined Content-Length. |
412 | Precondition Failed | The server did not satisfy one of the preconditions set by the requester in the request. |
413 | Request Entity Too Large | The server refused the request because the request was too large. The server may close the connection to prevent the client from continuously sending the request. If the server is only temporarily unable to process the request, a response message with Retry-After will be included. |
414 | Request URI Too Long | The URI requested by the client is too long for the server to process. |
415 | Unsupported Media Type | The server cannot process the media format attached to the request. |
416 | Requested Range Not Satisfiable | The range requested by the client is invalid. |
417 | Expectation Failed | The expectation given in the request's Expect header could not be met. |
422 | Unprocessable Entity | The request format is correct, but cannot be responded to due to semantic errors. |
429 | Too Many Requests | The client has sent more requests than the rate limit allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. 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 can be accessed by the request, but it cannot understand the user's request. |
501 | Not Implemented | The server does not support the requested function and cannot fulfill the request. |
502 | Bad Gateway | As a gateway or proxy, the server has received an invalid request from a remote server. |
503 | Service Unavailable | The requested service is invalid. Modify the request directly and do not attempt to retry it. |
504 | Gateway Timeout | The request cannot be fulfilled within the given duration. The client will only receive this response when a timeout parameter is specified for the request. |
505 | HTTP Version Not Supported | The server does not support the requested version of the HTTPS protocol and cannot fulfill the request. |