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. This code indicates that the server has received and is processing the request, but no response is available yet....

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 (e.g. a Web accelerator) 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. Unlike a 204 response, this response requires that the requester reset the document view...

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 e...

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

he 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. This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary re...

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

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. For security reasons, many HTTP clients (such as Mozilla Fi...

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 o...

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 permanentl...

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)....

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 th...

Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or...

The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited...

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible....

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 P...

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.[39]...

The client must first authenticate itself with the proxy....

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 tim...

Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between ...

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 sho...

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. Previously called "Request Entity Too Large....

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, ...

The request entity has a media type which the server or resource does not support. For example, the client up...

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 server cannot meet the requirements of the Expect request-header field....

This code was defined in 1998 as one of the traditional IETF ...

The request was directed at a server that is not able to produce a response[56] (for example because of connection...

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 (e.g., a PROPPATCH)....

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.0, given in the ...

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 user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes...

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