HTTPCode.printAll(...) Output
100 Continue
Description: 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)
Category: Informational response
101 Switching Protocols
Description: The requester has asked the server to switch protocols and the server has agreed to do so.
Category: Informational response
102 Processing
Description: 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.
Category: Informational response
103 Early Hints
Description: Used to return some response headers before final HTTP message.
Category: Informational response
200 OK
Description: 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.
Category: Success
201 Created
Description: The request has been fulfilled, resulting in the creation of a new resource.
Category: Success
202 Accepted
Description: 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.
Category: Success
203 Non-Authoritative Information
Description: 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.
Category: Success
204 No Content
Description: The server successfully processed the request and is not returning any content.
Category: Success
205 Reset Content
Description: 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.
Category: Success
206 Partial Content
Description: 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.
Category: Success
207 Multi-Status
Description: 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.
Category: Success
208 Already Reported
Description: The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
Category: Success
226 IM Used
Description: 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.
Category: Success
300 Multiple Choices
Description: 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.
Category: Redirection
301 Moved Permanently
Description: This and all future requests should be directed to the given URI.
Category: Redirection
302 Found, Moved temporarily
Description: 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.
Category: Redirection
303 See Other
Description: 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.
Category: Redirection
304 Not Modified
Description: 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.
Category: Redirection
305 Use Proxy
Description: The requested resource is available only through a proxy, the address for which is provided in the response. Many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
Category: Redirection
306 Switch Proxy
Description: No longer used. Originally meant 'Subsequent requests should use the specified proxy.'
Category: Redirection
307 Temporary Redirect
Description: 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.
Category: Redirection
308 Permanent Redirect
Description: 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.
Category: Redirection
400 Bad Request
Description: 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).
Category: Client errors
401 Unauthorized
Description: 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 'unauthenticated', i.e. the user does not have the necessary credentials.
Category: Client errors
402 Payment Required
Description: 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 usually 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.
Category: Client errors
403 Forbidden
Description: The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.
Category: Client errors
404 Not Found
Description: The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
Category: Client errors
405 Method Not Allowed
Description: 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.
Category: Client errors
406 Not Acceptable
Description: The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.
Category: Client errors
407 Proxy Authentication Required
Description: The client must first authenticate itself with the proxy.
Category: Client errors
408 Request Timeout
Description: 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.'
Category: Client errors
409 Conflict
Description: 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.
Category: Client errors
410 Gone
Description: 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.
Category: Client errors
411 Length Required
Description: The request did not specify the length of its content, which is required by the requested resource.
Category: Client errors
412 Precondition Failed
Description: The server does not meet one of the preconditions that the requester put on the request.
Category: Client errors
413 Payload Too Large
Description: The request is larger than the server is willing or able to process. Previously called 'Request Entity Too Large'.
Category: Client errors
414 URI Too Long
Description: 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.
Category: Client errors
415 Unsupported Media Type
Description: 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.
Category: Client errors
416 Range Not Satisfiable
Description: 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.
Category: Client errors
417 Expectation Failed
Description: The server cannot meet the requirements of the Expect request-header field.
Category: Client errors
418 I'm a teapot
Description: 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.
Category: Client errors
421 Misdirected Request
Description: The request was directed at a server that is not able to produce a response (for example because of connection reuse).
Category: Client errors
422 Unprocessable Entity
Description: The request was well-formed but was unable to be followed due to semantic errors.
Category: Client errors
423 Locked
Description: The resource that is being accessed is locked.
Category: Client errors
424 Failed Dependency
Description: The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).
Category: Client errors
425 Too Early
Description: Indicates that the server is unwilling to risk processing a request that might be replayed.
Category: Client errors
426 Upgrade Required
Description: The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.
Category: Client errors
428 Precondition Required
Description: 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.
Category: Client errors
429 Too Many Requests
Description: The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.
Category: Client errors
431 Request Header Fields Too Large
Description: The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
Category: Client errors
451 Unavailable For Legal Reasons
Description: 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).
Category: Client errors
500 Internal Server Error
Description: A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Category: Server errors
501 Not Implemented
Description: 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).
Category: Server errors
502 Bad Gateway
Description: The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Category: Server errors
503 Service Unavailable
Description: The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.
Category: Server errors
504 Gateway Timeout
Description: The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Category: Server errors
505 HTTP Version Not Supported
Description: The server does not support the HTTP protocol version used in the request.
Category: Server errors
506 Variant Also Negotiates
Description: Transparent content negotiation for the request results in a circular reference.
Category: Server errors
507 Insufficient Storage
Description: The server is unable to store the representation needed to complete the request.
Category: Server errors
508 Loop Detected
Description: The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
Category: Server errors
510 Not Extended
Description: Further extensions to the request are required for the server to fulfil it.
Category: Server errors
511 Network Authentication Required
Description: 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).
Category: Server errors
103 Checkpoint
Description: Used in the resumable requests proposal to resume aborted PUT or POST requests.
Category: Informational response
218 This is fine (Apache Web Server)
Description: Used as a catch-all error condition for allowing response bodies to flow through Apache when ProxyErrorOverride is enabled. When ProxyErrorOverride is enabled in Apache, response bodies that contain a status code of 4xx or 5xx are automatically discarded by Apache in favor of a generic response or a custom response specified by the ErrorDocument directive.
Category: Unofficial codes
419 Page Expired (Laravel Framework)
Description: Used by the Laravel Framework when a CSRF Token is missing or expired.
Category: Unofficial codes
420 Method Failure (Spring Framework)
Description: A deprecated response used by the Spring Framework when a method has failed.
Category: Unofficial codes
420 Enhance Your Calm (Twitter)
Description: Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead.
Category: Unofficial codes
450 Blocked by Windows Parental Controls (Microsoft)
Description: The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.
Category: Unofficial codes
498 Invalid Token (Esri)
Description: Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.
Category: Unofficial codes
499 Token Required (Esri)
Description: Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.
Category: Unofficial codes
509 Bandwidth Limit Exceeded (Apache Web Server/cPanel)
Description: The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.
Category: Unofficial codes
526 Invalid SSL Certificate
Description: Used by Cloudflare and Cloud Foundry's gorouter to indicate failure to validate the SSL/TLS certificate that the origin server presented.
Category: Unofficial codes
530 Site is frozen
Description: Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity.
Category: Unofficial codes
598 (Informal convention) Network read timeout error
Description: Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
Category: Unofficial codes
440 Login Time-out
Description: The client's session has expired and must log in again.
Category: Microsoft Internet Information Services
449 Retry With
Description: The server cannot honour the request because the user has not provided the required information.
Category: Microsoft Internet Information Services
451 Redirect
Description: Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users' mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.
Category: Client errors
444 No Response
Description: Used internally to instruct the server to return no information to the client and close the connection immediately.
Category: nginx
494 Request header too large
Description: Client sent too large request or too long header line.
Category: nginx
495 SSL Certificate Error
Description: An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
Category: nginx
496 SSL Certificate Required
Description: An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.
Category: nginx
497 HTTP Request Sent to HTTPS Port
Description: An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.
Category: nginx
499 Client Closed Request
Description: Used when the client has closed the request before the server could send a response.
Category: Unofficial codes
520 Unknown Error
Description: The 520 error is used as a 'catch-all response for when the origin server returns something unexpected', listing connection resets, large headers, and empty or invalid responses as common triggers.
Category: Cloudflare
521 Web Server Is Down
Description: The origin server has refused the connection from Cloudflare.
Category: Cloudflare
522 Connection Timed Out
Description: Cloudflare could not negotiate a TCP handshake with the origin server.
Category: Cloudflare
523 Origin Is Unreachable
Description: Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect.
Category: Cloudflare
524 A Timeout Occurred
Description: Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.
Category: Cloudflare
525 SSL Handshake Failed
Description: Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
Category: Cloudflare
526 Invalid SSL Certificate
Description: Cloudflare could not validate the SSL certificate on the origin web server.
Category: Unofficial codes
527 Railgun Error
Description: Error 527 indicates that the request timed out or failed after the WAN connection had been established.
Category: Cloudflare
530 Origin DNS Error
Description: Error 530 indicates that the requested host name could not be resolved on the Cloudflare network to an origin server.
Category: Unofficial codes