HTTP Status Codes

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

The server understands and is willing to comply with the client's request, via the Upgrade header field, for a change in the application protocol.

An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.

Used to return some response headers before final HTTP message.

Experimental code indicating the server supports resumable uploads.

The request was successful. The meaning of 'success' depends on the HTTP method (GET, POST, etc.).

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

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

The server successfully fulfilled the request and that there is no additional content to send in the response payload body.

The request was successful but the enclosed payload has been modified by a transforming proxy.

Tells the client to reset the document view, such as clearing a form.

The request has succeeded and the body contains the requested ranges of data.

Conveys information about multiple resources, for 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.

Indicates multiple options for the resource from which the client may choose.

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

Tells the client to look at (browse to) another URL temporarily.

Directs the client to get the requested resource at another URI with a GET request.

Tells the client that the cached version of the requested resource is still fresh and can be used.

Deprecated. Originally told the client to connect via a proxy.

Deprecated. No longer used.

Tells the client to get the resource at another URI with the same method that was used in the prior request.

The resource has permanently moved to a new URI, and the HTTP method must be preserved.

The server cannot or will not process the request due to something that is perceived to be a client error.

Although the HTTP standard specifies 'unauthorized', semantically this response means 'unauthenticated'.

Reserved for future use. Sometimes used by APIs to indicate quota limits or billing issues.

The client does not have access rights to the content.

The server can not find the requested resource.

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

The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.

Similar to 401 Unauthorized, but indicates that the client needs to authenticate itself in order to use a proxy.

The server timed out waiting for the request.

The request could not be completed due to a conflict with the current state of the target resource.

The requested resource is no longer available and will not be available again.

The server refuses to accept the request without a defined Content-Length.

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 in the request cannot be fulfilled.

This response code means the expectation indicated by the Expect request header field cannot be met by the server.

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 was unable to be followed due to semantic errors.

The source or destination resource of a method is locked.

The method could not be performed on the resource because the requested action depended on another action and that action failed.

Indicates that 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 be willing to do so after the client upgrades 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 (rate limiting).

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

The user 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, acting as a gateway or proxy, received an invalid response from the upstream server.

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version that was used in the request.

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself.

The server is unable to store the representation needed to complete the request.

The server terminated an operation because it encountered an infinite loop while processing a request.

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

The client needs to authenticate to gain network access.