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.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message.
The request has succeeded.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but it has not been completed.
The returned metadata is from a copy that may not be authoritative.
The server successfully processed the request and is not returning any content.
Tells the client to reset the document view that caused the request.
Partial GET response for a Range request.
Conveys information about multiple resources (WebDAV).
Members of a DAV binding have already been enumerated.
Response represents the result of one or more instance-manipulations.
Multiple options for the resource the client may follow.
The resource has been assigned a new permanent URI.
The resource resides temporarily at a different URI.
Response can be found at another URI using a GET method.
The resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI; the method must not change.
Permanent redirect; the request method must not change.
The server cannot or will not process the request due to a client error.
Authentication is required and has failed or has not yet been provided.
Reserved for future use.
The request was valid but the server is refusing action.
The requested resource could not be found.
The request method is not supported for the resource.
The resource cannot generate content acceptable according to the Accept headers.
The client must first authenticate with the proxy.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The resource is no longer available and will not be available again.
The request did not specify the length of its content.
The server does not meet one of the preconditions in the request.
The request entity 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 the server does not support.
The client asked for a portion of the file that the server cannot supply.
The server cannot meet the requirements of the Expect header.
The server refuses the attempt to brew coffee with a teapot.
The request was directed at a server that is not able to produce a response.
The request was well-formed but had semantic errors.
The resource being accessed is locked.
The request failed due to failure of a previous request.
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 for legal reasons.
A generic error message when no more specific message is suitable.
The server does not recognize the request method or lacks the ability to fulfill it.
The server was acting as a gateway and received an invalid response from the upstream.
The server is currently unavailable (overloaded or down for maintenance).
The upstream server failed to send a request in the time allowed.
The server does not support the HTTP protocol version used in the request.
Transparent content negotiation 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 fulfill it.
The client needs to authenticate to gain network access.