Response Status Code | Reason | Description |
|---|---|---|
100 | Continue | Indicates that the initial part of a request has been received and has not yet been rejected by the server. |
101 | Switching Protocols | Indicates a protocol to which the server switches. |
102 | Processing | Indicates that the server has accepted the complete request but has not yet completed it. |
200 | OK | Indicates that the request has succeeded. |
201 | Created | Indicates that the request has been fulfilled and has resulted in one or more new resources being created. |
202 | Accepted | Indicates that the request has been accepted for processing but the processing has not been completed. |
203 | Non-Authoritative Information | Indicates that the request was successful but the enclosed payload has been modified from the origin server's 200 (OK) response by a transforming proxy. |
204 | No Content | Indicates that the server has successfully fulfilled the request and there is no additional content to send in the response payload body. |
205 | Reset Content | Indicates that the server has fulfilled the request and wants the user agent to reset the document view to its original state as received from the origin server. |
206 | Partial Content | Indicates that the request has succeeded and the body contains the requested ranges of data as described in the Range header of the request. |
207 | Multi-Status | Conveys information about multiple resources in situations where multiple status codes might be appropriate. |
208 | Already Reported | Indicates that the members of a Distributed Authoring and Versioning (DAV) binding have already been enumerated in a preceding part of the multi-status response and are not being included again. |
226 | IM Used | Indicates that the server has fulfilled a client's request for a given resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. |
300 | Multiple Choices | Indicates that the request has more than one possible response. The user-agent or the user should choose one of them. |
301 | Moved Permanently | Indicates that the target resource has been assigned a new permanent URI and any future references to this resource must use one of the enclosed URIs. |
302 | Found | Indicates that the target resource resides temporarily under a different URI. |
303 | See Other | Indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request. |
304 | Not Modified | Indicates that a conditional GET or HEAD request has been received and would have resulted in a 200(OK) response if the condition had not evaluated as false. |
305 | Use Proxy | Indicates a deprecated status code. |
306 | (Unused) | Indicates a reserved code defined in a previous version of HTTP/1.1, which is no longer used. |
307 | Temporary Redirect | Indicates that the target resource resides temporarily under a different URI and the user agent must not change the request method if it performs an automatic redirection to that URI. |
308 | Permanent Redirect | Indicates that the target resource has been assigned a new permanent URI and any future references to this resource must use one of the enclosed URIs. |
400 | Bad Request | Indicates that the server cannot or will not process the request due to something that is perceived to be a client error such as a malformed request syntax, invalid request message framing, or deceptive request routing. |
401 | Unauthorized | Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. |
402 | Payment Required | Indicates a nonstandard response status code that is reserved for future use. |
403 | Forbidden | Indicates that the server understood the request but refuses to authorize it. |
404 | Not Found | Indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists. |
405 | Method Not Allowed | Indicates that the method received in the request-line is known by the origin server but not supported by the target resource. |
406 | Not Acceptable | Indicates that the target resource does not have a current representation that is acceptable to the user agent, according to the proactive negotiation header fields received in the request content negotiation, and the server is unwilling to supply a default representation. |
407 | Proxy Authentication Required | Similar to 401 (Unauthorized) but indicates that the client needs to authenticate itself to use a proxy. |
408 | Request Timeout | Indicates that the server did not receive a complete request message within the time that it was prepared to wait. |
409 | Conflict | Indicates that the request could not be completed due to a conflict with the current state of the target resource. |
410 | Gone | Indicates that access to the target resource is no longer available at the origin server and this condition is likely to be permanent. |
411 | Length Required | Indicates that the server refuses to accept the request without a defined Content-Length. |
412 | Precondition Failed | Indicates that one or more conditions given in the request header fields evaluated to false when tested on the server. |
413 | Payload Too Large | Indicates that the server is refusing to process a request because the request payload is larger than what the server is willing or able to process. |
414 | URI Too Long | Indicates that the server is refusing to service the request because the request-target is longer than what the server is willing to interpret. |
415 | Unsupported Media Type | Indicates that the origin server is refusing to service the request because the payload is in a format that is not supported by this method on the target resource. |
416 | Range Not Satisfiable | Indicates that none of the ranges in the request's Range header field overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid ranges or an excessive request of small or overlapping ranges. |
417 | Expectation Failed | Indicates that the expectation given in the request's Expect header field could not be met by at least one of the inbound servers. |
422 | Unprocessable Entity | Indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. |
423 | Locked | Indicates that the source or destination resource of a method is locked. |
424 | Failed Dependency | Indicates that the method could not be performed on the resource because the requested action depended on another action that failed. |
426 | Upgrade Required | Indicates that the server refuses to process the request using the current protocol but might be able to after the client upgrades to a different protocol. |
428 | Precondition Required | Indicates that the server requires the request to be conditional. This means that a required precondition header, such as If-Match, is missing. |
429 | Too Many Requests | Indicates that the user has sent too many requests in a given period of time. |
431 | Request Header Fields Too Large | Indicates that the server refuses to process the request because the request's HTTP headers are too long. |
500 | Internal Server Error | Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. |
501 | Not Implemented | Indicates that the server does not support the functionality required to fulfil the request. |
502 | Bad Gateway | Indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfil the request. |
503 | Service Unavailable | Indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be resolved after some time. |
504 | Gateway Timeout | Indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access to complete the request. |
505 | HTTP Version Not Supported | Indicates that the server does not support, or refuses to support, the major version of HTTP that was used in the request message. |
506 | Variant Also Negotiates | It might be given in the context of Transparent Content Negotiation. This protocol enables a client to retrieve the best variant of a given resource, where the server supports multiple variants. |
507 | Insufficient Storage | Indicates that the server is unable to store the representation needed to complete the request. |
508 | Loop Detected | Indicates that the server terminated an operation because it encountered an infinite loop while processing a request with Depth: infinity. |
510 | Not Extended | Indicates that the request did not meet the policy for accessing the resource. The server should send back all the information necessary for the client to issue an extended request. It is outside the scope of this specification to specify how the extensions inform the client. |
511 | Network Authentication Required | Indicates that the client needs to authenticate to gain network access. |