||This means that the server has received the request headers, and that 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). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).
||This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
||Processing (WebDAV; RFC2518)
||As a WebDAV request may contain many sub-requests involving file operations, it may take 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.
||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.
||The request has been fulfilled and resulted in a new resource being created.
||The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
||Non-Authoritative Information (since HTTP/1.1)
||The server successfully processed the request, but is returning information that may be from another source.
||The server successfully processed the request, but is not returning any 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.
|| Partial Content
||The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
||Multi-Status (WebDAV; RFC 4918)
||The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
||Already Reported (WebDAV; RFC 5842)
||The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.
||IM Used (RFC 3229)
||The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
||SIndicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
||This and all future requests should be directed to the given URI.
||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.
||See Other (since HTTP/1.1)
||The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
||Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-Match. This means that there is no need to retransmit the resource, since the client still has a previously-downloaded copy.
||Use Proxy (since HTTP/1.1)
||The requested resource is only available through a proxy, whose address is provided in the response. Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
||No longer used. Originally meant Subsequent requests should use the specified proxy.
||Temporary Redirect (since HTTP/1.1)
||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 instance, a POST request should be repeated using another POST request.
||Permanent Redirect (approved as experimental RFC)
||The request, and all future requests should be repeated using another URI. 307 and 308 (as proposed) parallel the behaviours 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.
||The request cannot be fulfilled due to bad syntax..
||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.
||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, but that has not happened, and this code is not usually used. As an example of its use, however, Apple's defunct MobileMe service generated a 402 error if the MobileMe account was delinquent. In addition, YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPTCHA.
||The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g. a recognized user attempting to access restricted content)
||The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
||Method Not Allowed
||A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
||The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
||Proxy Authentication Required
||The client must first authenticate itself with the proxy.
||The server timed out waiting for the request. According to W3 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.
||Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
||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 again 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.
||The request did not specify the length of its content, which is required by the requested resource.
||The server does not meet one of the preconditions that the requester put on the request.
||Request Entity Too Large
||The request is larger than the server is willing or able to process.
||Request-URI Too Long
||The URI provided was too long for the server to process.
||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.
||Requested Range Not Satisfiable
||The client has asked for a portion of the file, 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.
||The server cannot meet the requirements of the Expect request-header field.
||I'm a teapot (RFC 2324)
||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.
||Enhance Your Calm (Twitter)
||Not part of the HTTP standard, but returned by the Twitter Search and Trends API when the client is being rate limited. Other services may wish to implement the 429 Too Many Requests response code instead.
||Unprocessable Entity (WebDAV; RFC 4918)
||NThe request was well-formed but was unable to be followed due to semantic errors.
||Locked (WebDAV; RFC 4918)
||The resource that is being accessed is locked.
||Method Failure (WebDAV)
||Indicates the method was not executed on a particular resource within its scope because some part of the method's execution failed causing the entire method to be aborted.
||Unordered Collection (Internet draft)
||Defined in drafts of 'WebDAV Advanced Collections Protocol', but not present in Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol
||Upgrade Required (RFC 2817)
||The client should switch to a different protocol such as TLS/1.0.
||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.
||Too Many Requests
||The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.
||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.
||No Response (Nginx)
||Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection (useful as a deterrent for malware).
||Retry With (Microsoft)
||A Microsoft extension. The request should be retried after performing the appropriate action. Often search-engines or custom applications will ignore required parameters. Where no default action is appropriate, the Aviongoo website sends a "HTTP/1.1 449 Retry with valid parameters: param1, param2, . . ." response. The applications may choose to learn, or not.
||Blocked by Windows Parental Controls (Microsoft)
||A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
||Used in Exchange ActiveSync if there either is a more efficient server to use or the server can't access the users' mailbox. The client is supposed to re-run the HTTP Autodiscovery protocol to find a better suited server.
||Request Header Too Large (Nginx)
||Nginx internal code similar to 431 but it was introduced earlier.
||Cert Error (Nginx)
||Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection.
||No Cert (Nginx)
||Nginx internal code used when client didn't provide certificate to distinguish it from 4XX in a log and an error page redirection.
||HTTP to HTTPS (Nginx)
||Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection.
||Client Closed Request (Nginx)
||Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back.
||Internal Server Error
||A generic error message, given when no more specific message is suitable.
||The server either does not recognize the request method, or it lacks the ability to fulfil the request.
||The server was acting as a gateway or proxy and received an invalid response from the upstream server.
||The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
||The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
||HTTP Version Not Supported
||The server does not support the HTTP protocol version used in the request.
||Variant Also Negotiates (RFC 2295)
||Transparent content negotiation for the request results in a circular reference.
||Insufficient Storage (WebDAV; RFC 4918)
||The server is unable to store the representation needed to complete the request.
||Loop Detected (WebDAV; RFC 5842)
||The server detected an infinite loop while processing the request (sent in lieu of 208).
||Bandwidth Limit Exceeded (Apache bw/limited extension)
||This status code, while used by many servers, is not specified in any RFCs.
||Not Extended (RFC 2774)
||Further extensions to the request are required for the server to fulfil it.
||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).
||Network read timeout error (Unknown)
||This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
||Network connect timeout error (Unknown)
||This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.