The request has succeeded. The meaning depends on the HTTP method used.

The request has been fulfilled and resulted in a new resource being created.

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

The returned meta-information is not from the origin server.

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

The server successfully processed the request, but is not returning any content and requires the requester to 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 contains multiple status codes for multiple independent operations.

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

The server cannot process the request due to client error.

Authentication is required and has failed or not been provided.

Reserved for future use.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

The method specified in the request is not allowed for the resource.

The resource is not capable of generating content acceptable according to Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

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

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

The request did not specify the length of its content required by the resource.

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

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 media format of the requested data is not supported by the server.

The range specified in the Range header cannot be fulfilled.

The server cannot meet the requirements of the Expect request-header field.

The server refuses to brew coffee because it is 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 was unable to be followed due to semantic errors.

The resource that is being accessed is locked.

The request failed due to failure of a previous request.

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

The resource is unavailable due to legal demands.