HTTP Status Codes

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

The server is switching protocols as requested by the client.

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

The request has succeeded.

The request has been fulfilled and a new resource has been created.

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

The returned meta-information is from a local or third-party copy, not the origin server.

The server has fulfilled the request but does not need to return an entity-body.

The server has fulfilled the request and the user agent should reset the document view.

The server has fulfilled the partial GET request for the resource.

The message body that follows is an XML message with multiple response codes.

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

The server has fulfilled a GET request for the resource with instance manipulations.

The requested resource has multiple choices, each with a different URI.

The requested resource has been assigned a new permanent URI.

The requested resource resides temporarily under a different URI.

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

The resource has not been modified since the last request.

The requested resource must be accessed through the proxy given by the Location field.

The requested resource resides temporarily under a different URI.

The requested resource has been assigned a new permanent URI.

The server could not understand the request due to malformed syntax.

The request requires user authentication.

This code is reserved for future use.

The server understood the request, but is refusing to fulfill it.

The server has not found anything matching the Request-URI.

The method specified in the Request-Line is not allowed for the identified resource.

The resource identified by the request is not capable of generating response entities.

The client must first authenticate itself with the proxy.

The client did not produce a request within the time the server was prepared to wait.

The request could not be completed due to a conflict with the current state of the resource.

The requested resource is no longer available at the server and no forwarding address is known.

The server refuses to accept the request without a defined Content-Length.

The precondition given in one or more of the request-header fields evaluated to false.

The server is refusing to process a request because the request payload is larger than the server is willing to process.

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.

The server is refusing to service the request because the entity of the request is in a format not supported.

The requested Range header field cannot be fulfilled.

The expectation given in the Expect header field could not be met by the server.

The resulting entity body may be short and stout.

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

The server understands the content type and syntax but was unable to process the contained instructions.

The source or destination resource of a method is locked.

The method could not be performed because the requested action depended on another action that failed.

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 its header fields are too large.

The server is denying access to the resource as a consequence of a legal demand.

The server encountered an unexpected condition which prevented it from fulfilling the request.

The server does not support the functionality required to fulfill the request.

The server received an invalid response from the upstream server.

The server is currently unable to handle the request due to temporary overloading or maintenance.

The server did not receive a timely response from the upstream server.

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

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

The method could not be performed on the resource because the server is unable to store the representation.

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.

The client closed the connection before the server could respond. (Nginx non-standard)

The origin server returned an unknown or unexpected response. (Cloudflare)

The origin server has refused the connection from Cloudflare. (Cloudflare)

Cloudflare could not negotiate a TCP handshake with the origin server. (Cloudflare)

Cloudflare could not reach the origin server. (Cloudflare)

Cloudflare established a TCP connection but did not receive a timely HTTP response. (Cloudflare)