HTTP Status Codes

The server has received the request headers and the client should proceed to send the request body.

The server is switching protocols as requested (e.g., from HTTP to WebSocket).

Server has received and is processing the request, but no response is available yet (WebDAV).

Used to return some response headers before the final HTTP message.

The request has succeeded.

The request has succeeded and a new resource has been created.

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

The returned metadata is from a cached copy or third-party source, not the origin server.

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

The server processed the request and asks the client to reset the document view.

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

Multiple status codes might be appropriate (WebDAV). Body contains XML.

The members of a DAV binding have already been enumerated.

The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations.

Multiple options for the resource are available. The user should select one.

The resource has been permanently moved to a new URL.

The resource is temporarily at a different URL.

The response can be found at a different URI using a GET method.

The resource has not been modified since the version specified in the request headers.

The requested resource must be accessed through the proxy given in the Location field. (Deprecated)

The request should be repeated with another URI, but future requests should still use the original URI.

The request and all future requests should be repeated using another URI (method preserved).

The server could not understand the request due to invalid syntax.

Authentication is required and has failed or has not yet been provided.

Reserved for future use. Originally intended for digital payment systems.

The client does not have access rights to the content.

The server could not find the requested resource.

The request method is known but has been disabled and cannot be used.

No content matching the criteria given by the user agent is found.

Authentication with the proxy is required before the request can proceed.

The server would like to shut down this unused connection.

The request conflicts with the current state of the server.

The requested content has been permanently deleted from server.

Server rejected the request because the Content-Length header is not defined.

The client has indicated preconditions in its headers which the server does not meet.

The request entity is larger than limits defined by server.

The URI requested by the client is longer than the server is willing to interpret.

The media format of the requested data is not supported by the server.

The range specified by the Range header cannot be fulfilled.

The expectation given in the Expect request-header field cannot be met by the server.

The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324 April Fool's joke)

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

The request failed because it depended on another request which failed (WebDAV).

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

The server refuses to perform the request using the current protocol but will after a protocol upgrade.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time (rate limiting).

The server is unwilling to process the request because its header fields are too large.

The user agent requested a resource that cannot legally be provided.

The server has encountered a situation it does not know how to handle.

The request method is not supported by the server and cannot be handled.

The server got an invalid response while working as a gateway.

The server is not ready to handle the request — temporarily overloaded or down for maintenance.

The server is acting as a gateway and cannot get a response in time.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error.

The method could not be performed because the server cannot store the representation needed (WebDAV).

The server detected an infinite loop while processing the request (WebDAV).

Further extensions to the request are required for the server to fulfill it.

The client needs to authenticate to gain network access.