HTTP Errors Reference
This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the HTTP. The first digit of the status code specifies one of five standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).
An informational response indicates that the request was received and understood. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.
The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role. There are five classes defined by the standard:
1xx informational response – the request was received, continuing process
2xx successful – the request was successfully received, understood, and accepted
3xx redirection – further action needs to be taken in order to complete the request
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection. A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD. A user agent may automatically redirect a request. A user agent should detect and intervene to prevent cyclical redirects.
4xx client error – the request contains bad syntax or cannot be fulfilled
5xx server error – the server failed to fulfill an apparently valid request
The server failed to fulfill a request. Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.
|1||Error 100: Continue|| |
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) then it shouldn't send the request's body. The response 417 Expectation Failed indicates that the request should be repeated without the Expect header as it indicates that the server doesn't support expectations (this is the case, for example, of HTTP/1.0 servers).
|2||Error 101: Switching: Protocols|| |
The requester has asked the server to switch protocols and the server has agreed to do so.
|3||Error 102: Processing|| |
A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
|4||Error 200: Ok|| |
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
|5||Error 201: Created|| |
The request has been fulfilled, resulting in the creation of a new resource.
|6||Error 202: Accepted|| |
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.
|7||Error 203: Non: Authoritative|| |
The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.
|8||Error 204: No: Content|| |
The server successfully processed the request and is not returning any content.
|9||Error 205: Reset: Content|| |
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
|10||Error 206: Partial: Content|| |
The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
|11||Error 207: Multi: Status|| |
The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
|12||Error 300: Multiple: Choices|| |
Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.
|13||Error 301: Moved: Permanently|| |
This and all future requests should be directed to the given URI.
|14||Error 302: Moved: Temporarily|| |
Tells the client to look at (browse to) another URL. 302 has been superseded by 303 and 307. This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web applications and frameworks use the 302 status code as if it were the 303.
|15||Error 303: See: Other|| |
The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.
|16||Error 304: Not: Modified|| |
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
|17||Error 305: Use: Proxy|| |
The requested resource is available only through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not obey this status code.
|18||Error 307: Temporary: Redirect|| |
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.
|19||Error 400: Bad: Request|| |
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
|20||Error 401: Unauthorized|| |
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means "unauthorised", the user does not have valid authentication credentials for the target resource. Note: Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.
|21||Error 402: Payment: Required|| |
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler, but that has not yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests. Sipgate uses this code if an account does not have sufficient funds to start a call. Shopify uses this code when the store has not paid their fees and is temporarily disabled. Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.
|22||Error 403: Forbidden|| |
The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication via the WWW-Authenticate header field, but the server did not accept that authentication. The request should not be repeated.
|23||Error 404: Not: Found|| |
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
|24||Error 405: Method: Not: Allowed|| |
A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.
|25||Error 406: Not: Acceptable|| |
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.
|26||Error 407: Proxy: Authentication: Required|| |
The client must first authenticate itself with the proxy.
|27||Error 408: Request: Time: Out|| |
The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."
|28||Error 409: Conflict|| |
Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.
|29||Error 410: Gone|| |
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
|30||Error 411: Length: Required|| |
The request did not specify the length of its content, which is required by the requested resource.
|31||Error 412: Precondition: Failed|| |
The server does not meet one of the preconditions that the requester put on the request header fields.
|32||Error 413: Request: Entity: Too: Large|| |
The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".
|33||Error 414: Request: Uri: Too: Large|| |
The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.
|34||Error 415: Unsupported: Media: Type|| |
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
|35||Error 416: Range: Not: Satisfiable|| |
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously.
|36||Error 417: Expectation: Failed|| |
The server cannot meet the requirements of the Expect request-header field.
|37||Error 422: Unprocessable: Entity|| |
The request was well-formed but was unable to be followed due to semantic errors.
|38||Error 423: Locked|| |
The resource that is being accessed is locked.
|39||Error 424: Failed: Dependency|| |
The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).
|40||Error 426: Upgrade: Required|| |
The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.
|41||Error 500: Internal: Server: Error|| |
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
|42||Error 501: Not: Implemented|| |
The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).
|43||Error 502: Bad: Gateway|| |
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
|44||Error 503: Service: Unavailable|| |
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.
|45||Error 504: Gateway: Time: Out|| |
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
|46||Error 505: Version: Not: Supported|| |
The server does not support the HTTP protocol version used in the request.
|47||Error 506: Variant: Also: Varies|| |
Transparent content negotiation for the request results in a circular reference.
|48||Error 507: Insufficient: Storage|| |
The server is unable to store the representation needed to complete the request.
|49||Error 510: Not: Extended|| |
Further extensions to the request are required for the server to fulfill it.
|50||103 Early Hints (RFC 8297)|| |
Used to return some response headers before final HTTP message.
|51||208 Already Reported (WebDAV; RFC 5842)|| |
The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
|52||226 IM Used (RFC 3229)|| |
The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
|53||306 Switch Proxy|| |
No longer used. Originally meant "Subsequent requests should use the specified proxy."
|54||308 Permanent Redirect (RFC 7538)|| |
The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.
|55||418 I'm a teapot (RFC 2324, RFC 7168)|| |
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee. This HTTP status is used as an Easter egg in some websites, including Google.com.
|56||421 Misdirected Request (RFC 7540)|| |
The request was directed at a server that is not able to produce a response (for example because of connection reuse).
|57||425 Too Early (RFC 8470)|| |
Indicates that the server is unwilling to risk processing a request that might be replayed.
|58||428 Precondition Required (RFC 6585)|| |
The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
|59||429 Too Many Requests (RFC 6585)|| |
The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.
|60||431 Request Header Fields Too Large (RFC 6585)|| |
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
|61||451 Unavailable For Legal Reasons (RFC 7725)|| |
A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource. The code 451 was chosen as a reference to the novel Fahrenheit 451 (see the Acknowledgements in the RFC).
|62||508 Loop Detected (WebDAV; RFC 5842)|| |
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
|63||511 Network Authentication Required (RFC 6585)|| |
The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).