The table below lists the status codes that may be used in HTTP response messages as defined in RFC 7231 and RFC 6585.
You can filter the table contents by typing a code, name, or class into the Search field. Click on an arrow in a column header to sort the visible entries by that column.
Code |
Name |
Class |
Description |
| 100 | Continue | Informational | This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished. |
| 101 | Switching Protocols | Informational | Indicates that the server understands and is willing to comply with the client's request, via the Upgrade header field, for a change in the application protocol being used on this connection. |
| 200 | OK | Successful | Indicates that the request has succeeded. The payload sent depends on the request method. |
| 201 | Created | Successful | Indicates that the request has been fulfilled and has resulted in one or more new resources being created. |
| 202 | Accepted | Successful | Indicates that the request has been accepted for processing but the processing has not been completed. |
| 203 | Non-Authoritative Information | Successful | Indicates that the request was successful but the enclosed payload has been modified from that of the origin server's 200 response by a transforming proxy. |
| 204 | No Content | Successful | Indicates that the server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| 205 | Reset Content | Successful | Indicates that the server has fulfilled the request and desires that the user agent reset the document view, which caused the request to be sent, to its original state as received from the origin server. |
| 300 | Multiple Choices | Redirect | Indicates that the target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to one or more of those identifiers. |
| 301 | Moved Permanently | Redirect | Indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs. |
| 302 | Found | Redirect | Indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the effective request URI for future requests. |
| 303 | See Other | Redirect | Indicates that the server is redirecting the user agent to a different resource, as specified by a URI in the Location header field, which is intended to provide an indirect response to the original request. |
| 305 | Use Proxy | Redirect | Deprecated |
| 306 | (Unused) | Redirect | This code is no longer used and is reserved. |
| 307 | Temporary Redirect | 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. Since the redirection can change over time, the client should continue using the original URI for future requests. |
| 400 | Bad Request | Client Error | Indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g. malformed request syntax, invalid request message framing, or deceptive request routing). |
| 402 | Payment Required | Client Error | Reserved for future use. |
| 403 | Forbidden | Client Error | Indicates that the server understood the request but refuses to authorize it. If authentication credentials were provided in the request, the server considers then insufficient to grant access. |
| 404 | Not Found | Client Error | 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 | Client Error | Indicates that the method received in the request line is known by the origin server but not supported by the target resource. The origin server must generate an Allow header field in the response containing a list of the target resource's currently supported methods. |
| 406 | Not Acceptable | Client Error | Indicates that the target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request, and the server is unwilling to supply a default representation. |
| 408 | Request Timeout | Client Error | Indicates that the server did not receive a complete request message within the time that it was prepared to wait. A server should send the "close" connection option in the response. |
| 409 | Conflict | Client Error | Indicates that the request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request. |
| 410 | Gone | Client Error | Indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent. |
| 411 | Length Required | Client Error | Indicates that the server refuses to accept the request without a defined Content-Length. |
| 413 | Payload Too Large | Client Error | Indicates that the server is refusing to process a request because the request payload is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request. |
| 414 | URI Too Long | Client Error | Indicates that the server is refusing to service the request because the request target is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | Client Error | Indicates that the origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource. |
| 417 | Expectation Failed | Client Error | Indicates that the expectation given in the request's Expect header field could not be met by at least one of the inbound servers. |
| 426 | Upgrade Required | Client Error | Indicates that the server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server must send an Upgrade header field in the response to indicate the required protocol(s). |
| 428 | Precondition Required | Client Error | Indicates that the origin server requires the request to be conditional. Responses should explain how to resubmit the request successfully. |
| 429 | Too Many Requests | Client Error | Indicates that the user has sent too many requests in a given amount of time (rate limiting). The response should include details explaining the condition, and may include a Retry-After header indicating how long to wait before making a new request. |
| 431 | Request Header Fields Too Large | Client Error | Indicates that the server is unwilling to process the request because its header fields are too large. |
| 500 | Internal Server Error | Server Error | Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | Server Error | Indicates that the server does not support the functionality required to fulfill the request. |
| 502 | Bad Gateway | Server Error | Indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request. |
| 503 | Service Unavailable | Server Error | Indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. The server may send a Retry-After header field to suggest an appropriate amount of time for the client to wait before retrying the request. |
| 504 | Gateway Timeout | Server Error | 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 in order to complete the request. |
| 505 | HTTP Version Not Supported | Server Error | Indicates that the server does not support, or refuses to support, the major version of HTTP that was used in the request message. The server should generate a response that describes why that version is not supported and what other protocols are supported. |
| 511 | Network Authentication Required | Server Error | Indicates that the client needs to authenticate to gain network access. The response should contain a link to a resource that allows the user to submit credentials. |