HTTP Status Codes

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

The server is switching protocols as requested by the client (e.g., upgrading to WebSocket).

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

Used to return some response headers before the final HTTP message.

The request succeeded. The response body contains the requested data.

The request succeeded and a new resource was created as a result.

The request has been received but not yet acted upon.

The returned metadata is not exactly the same as from the origin server.

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

Tells the client to reset the document view.

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

The response body contains the status for multiple independent operations (WebDAV).

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

The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations.

There are multiple options for the resource that the client may follow.

The URL of the requested resource has been changed permanently.

The resource is temporarily located at a different URI.

The response to the request can be found at a different URI using the GET method.

The cached version of the resource is still valid.

The request should be repeated with the same method at a different URI.

The resource is now permanently located at another URI, specified by the Location header.

The server cannot process the request due to malformed syntax or invalid parameters.

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

Reserved for future use, sometimes used for digital payment requirements.

The client does not have access rights to the content.

The server cannot find the requested resource.

The HTTP method is known but has been disabled or is not supported for this resource.

The server cannot produce a response matching the criteria in the request's Accept headers.

Authentication must be done using a proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the server.

The resource is no longer available and will not be available again.

The request did not specify the Content-Length required by the server.

The server does not meet one of the preconditions specified in the request headers.

The request body is larger than the server is willing to accept.

The URI requested by the client is longer than the server is willing to interpret.

The request entity has a media type that the server does not support.

The range specified by the Range header cannot be fulfilled.

The expectation given in the Expect request-header field cannot be met by the server.

The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)

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

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

The resource that is being accessed is locked (WebDAV).

The request failed because it depended on another request that failed (WebDAV).

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

The client should switch to a different protocol.

The server requires the request to be conditional.

The user has sent too many requests in a given amount of time (rate limiting).

The server is unwilling to process the request because its header fields are too large.

The resource cannot legally be provided, such as due to government censorship.

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

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

The server, acting as a gateway, received an invalid response from an upstream server.

The server is temporarily unable to handle the request (overloaded or down for maintenance).

The server, acting as a gateway, did not receive a timely response from an upstream server.

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

The server has an internal configuration error.

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

The server detected an infinite loop while processing the request (WebDAV).

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

The client needs to authenticate to gain network access.