HTTP Status Code Lookup-- Complete 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 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. Helps the client start preloading resources.

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

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

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

The returned meta-information is from a local or third-party copy, not from the origin server.

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

The server successfully processed the request and is asking 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.

A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.

Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

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

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 may be made in the future.

The response to the request can be found under another URI using GET.

Indicates that the resource has not been modified since the version specified by the request headers.

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

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. Does not allow changing the HTTP method.

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.

Reserved for future use. Some APIs use this for rate limiting or payment-gated access.

The server understood the request but refuses to authorize it. Unlike 401, re-authenticating will not help.

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

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

The target resource does not have a current representation acceptable to the user agent.

The client must first authenticate itself with the proxy.

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

The request could not be processed because of conflict in 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, which is required by the requested resource.

The server does not meet one of the preconditions that the requester put on 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 by the Range header field in the request cannot be fulfilled.

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

The server refuses to brew coffee because it is, permanently, 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 because it depended on another request that failed.

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 might accept after the client upgrades.

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

The server is not ready to handle the request. Common causes are maintenance or overload.

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

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 (e.g., captive portal).