HTTP Status Code Lookup

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 via the Upgrade header.

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, allowing preloading resources.

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

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

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

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

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

The server successfully 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.

The message body contains multiple status codes for multiple independent operations (WebDAV).

The members of a DAV binding have already been enumerated and are not included again.

The server has fulfilled a request for the resource with instance-manipulations applied.

The request has more than one possible response. The user or user agent should choose one.

The URL of the requested resource has been changed permanently. The new URL is given in the response.

The URI of the requested resource has been changed temporarily. Further changes might be made in the future.

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

The resource has not been modified since last requested. The client can use its cached version.

The requested resource must be accessed through the proxy given by the Location field. Deprecated.

The server sends this response to redirect the client with the same method that was used in the prior request.

The resource is now permanently located at another URI, specified by the Location header. Same method must be used.

The server cannot process the request due to malformed syntax or invalid request message framing.

Authentication is required and has failed or has not been provided. The response must include a WWW-Authenticate header.

Reserved for future use. Some APIs use this to indicate a payment is required.

The client does not have access rights to the content. Unlike 401, the client identity is known to the server.

The server cannot find the requested resource. The URL is not recognized or the resource does not exist.

The request method is known by the server but not supported by the target resource.

The server cannot produce a response matching the list of acceptable values defined in the request headers.

Authentication is required by a proxy between the client and server.

The server timed out waiting for the request from the client.

The request conflicts with the current state of the server, usually due to concurrent modifications.

The content has been permanently deleted from the server with no forwarding address.

The 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 the 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 in the Range header cannot be fulfilled by the server.

The expectation given in the Expect request header could not be met by the server.

The server refuses the attempt to brew coffee with a teapot. An April Fools joke from RFC 2324.

The request was directed at a server that is not able to produce a response.

The request was well-formed but unable to be followed due to semantic errors (WebDAV).

The resource that is being accessed is locked (WebDAV).

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

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

The server refuses to perform the request using the current protocol but might do so with an upgrade.

The origin server requires the request to be conditional to prevent lost updates.

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 an unexpected condition that prevented it from fulfilling the request.

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

The server received an invalid response from the upstream server while acting as a gateway.

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

The server is acting as a gateway and did not get a response in time from the upstream server.

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

The server has an internal configuration error: transparent content negotiation results in a circular reference.

The server is unable to store the representation needed to complete the request (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, typically from a captive portal.