HTTP Status Code Reference

The server has received the request headers and 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 succeeded. The meaning depends on the HTTP method.

The request succeeded and a new resource was created as a result.

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

The returned metadata is not exactly the same as available from the origin server.

There is no content to send for this request, but the headers may be useful.

Tells the user agent to reset the document which sent this request.

This response is used for range requests.

The request has more than one possible response.

The URL of the requested resource has been changed permanently.

The URI of requested resource has been changed temporarily.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

The response has not been modified, so the client can continue to use the cached version.

The server sends this response to direct the client to get the requested resource at another URI with the same method.

The resource is permanently located at another URI, specified by the Location header.

The server cannot process the request due to client error (e.g., malformed request syntax).

The client must authenticate itself to get the requested response.

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

The client does not have access rights to the content.

The server cannot find the requested resource.

The request method is not supported for the requested resource.

The server cannot produce a response matching the list of acceptable values.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

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 field is not defined.

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

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 field cannot be fulfilled.

The expectation indicated by the Expect request header field cannot be met.

The server refuses the attempt to brew coffee with a teapot (April Fools' 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.

The request failed due to failure of a previous request.

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

The server refuses to perform the request using the current 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 its header fields are too large.

The user requested a resource that is not available due to legal reasons.

The server encountered an unexpected condition that prevented it from fulfilling the request.

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

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

The server is not ready to handle the request, often due to maintenance or overload.

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