HTTP Status Codes

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.

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 has successfully fulfilled the request and there is no content to send in the response payload.

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

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

The resource was found, but at a different URI temporarily.

The resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

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. 307 (Temporary Redirect) is preferred for temporary changes.

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.

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.

The method specified in the request line is known by the server but has been disabled and cannot be used.

The server did not receive a complete request message within the time that it was prepared to wait.

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

The target resource is no longer available at the origin server and that this condition is likely to be permanent.

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

The origin server is refusing to service the request because the payload's media type is not supported by this method on the target resource.

The server understands the content type of the request entity and the syntax of the request entity is correct, but was unable to process the contained instructions.

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

A generic error message, given when an unexpected condition was encountered.

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

The server was acting as a gateway or proxy and received an invalid response.

The server cannot handle the request (overloaded or down for maintenance).

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

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