HTTP Status Code Glossary

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.

A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.

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 of the origin's response.

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 client should reset the document view.

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

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.

The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.

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.

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

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

Tells the client to look at (browse to) another URL. 302 has been superseded by 303 and 307.

The response to the request can be found under another URI using the 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, the address for which is provided in the response.

In this case, 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.

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

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.

The request contained valid data and was understood by the server, 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 sent in the request.

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 current state of the resource.

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 header fields.

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 one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol.

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 because it depended on another request and that request failed.

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

The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.

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 that includes the requested resource.

A generic error message, given when an unexpected condition was encountered and 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 cannot handle the request (because it is 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 fulfil it.

The client needs to authenticate to gain network access.