HTTP Status Rabbits

The server has received the request headers and the client should proceed to send the request body.

The requester has asked the server to switch protocols and the server has agreed to do so.

The server has received and is processing the request, but no response is available yet.

Used to return some response headers before final HTTP message.

Standard response for successful HTTP requests.

The request has been fulfilled, resulting in the creation of a new resource.

The request has been accepted for processing, but the processing has not been completed.

The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version.

The server successfully processed the request and is not returning any content.

The server successfully processed the request, but is not returning any content.

The server is delivering only part of the resource due to a range header sent by the client.

The message body that follows is an XML message and can contain a number of separate response codes.

The members of a DAV binding have already been enumerated in a previous reply.

The server has fulfilled a request for the resource, and the response is a representation of the result.

Indicates multiple options for the resource from which the client may choose.

This and all future requests should be directed to the given URI.

The resource was found, but at a different URI.

The response to the request can be found under another URI using a GET method.

Indicates that the resource has not been modified since the version specified by the request headers.

The requested resource is available only through a proxy.

No longer used. Originally meant subsequent requests should use the specified proxy.

The request should be repeated with another URI; however, future requests should still use the original URI.

The request and all future requests should be repeated using another URI.

The server cannot or will not process the request due to an apparent client error.

Authentication is required and has failed or has not yet been provided.

Reserved for future use. The original intention was for digital payment systems.

The request was valid, but the server is refusing action.

The requested resource could not be found but may be available in the future.

A request method is not supported for the requested resource.

The requested resource is capable of generating only content not acceptable according to the Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

Indicates that the request could not be processed because of conflict in the request.

Indicates that the resource requested is no longer available and will not be available again.

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.

The request is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

The request entity has a media type which the server or resource does not support.

The client has asked for a portion of the file, but the server cannot supply that portion.

The server cannot meet the requirements of the Expect request-header field.

This code was defined in 1998 as an April Fools' joke and is not expected to be implemented by actual HTTP servers.

The request was directed at a server that is not able to produce a response.

The request was well-formed but was unable to be followed due to semantic errors.

The resource that is being accessed is locked.

The request failed due to failure of a previous request.

Indicates that the server is unwilling to risk processing a request that might be replayed.

The client should switch to a different protocol.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time.

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

A server operator has received a legal demand to deny access to a resource or to a set of resources.

Returned by the Twitter Search and Trends API when the client is being rate limited.

Used by Shopify to indicate that the request header fields are too large.

The client's session has expired and must log in again.

Used in nginx to indicate that the server has returned no information and closed the connection.

The server cannot honour the request because the user has not provided the required information.

A Microsoft extension indicating that Windows Parental Controls are turned on and blocking access.

Used by AWS Elastic Load Balancer to indicate that the client closed the connection.

Used by AWS Elastic Load Balancer when X-Forwarded-For header contains more than 30 IP addresses.

nginx internal code similar to 431.

nginx internal code used when SSL client certificate error occurred.

nginx internal code used when client did not provide certificate.

nginx internal code used when HTTP request was sent to HTTPS port.

Returned by ArcGIS for Server when a token is invalid or expired.

nginx internal code used when the client closes the connection while nginx is processing the request.

A generic error message when an unexpected condition was encountered.

The server either does not recognize the request method, or it lacks the ability to fulfill 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 (overloaded or down for maintenance).

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version used in the request.

Transparent content negotiation for the request results in a circular reference.

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing the request.

Further extensions to the request are required for the server to fulfill it.

The client needs to authenticate to gain network access.

Cloudflare error used when the origin server returns an unknown error.

Cloudflare error used when the origin server refuses the connection.

Cloudflare error used when the connection to the origin server times out.

Cloudflare error used when the origin server is unreachable.

Cloudflare error used when a connection was made but the origin server timed out before a response was received.

Cloudflare error used when the SSL/TLS handshake with the origin server fails.

Cloudflare error used when the origin server presents an invalid SSL certificate.

Cloudflare error used when there is an error with Cloudflare Railgun.

Used by Qualys in the SSLLabs server testing API to signal that the site cannot process the request.

Used by Cloudflare for sites under DDoS protection where access has been frozen.

Used by AWS Elastic Load Balancer for authentication errors.

Used by some HTTP proxies to signal a network read timeout behind the proxy.

Used by some HTTP proxies to signal a network connect timeout behind the proxy.