HTTP Status Code Reference

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

The server agrees to switch 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 preliminary HTTP headers (such as Link) before the final response is ready.

The request succeeded and the server returned the requested resource.

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 response is from a transforming proxy, not the origin server.

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

Tells the client to reset the document view that caused the request.

The server is delivering only part of the resource due to a Range header from the client.

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

The resource has been permanently moved to a new URL.

The resource is temporarily located at a different URL.

The response can be found under another URI using a GET method.

The cached version of the requested resource is still valid.

Like 302 but the request method must not change when following the redirect.

Like 301 but the request method must not change when following the redirect.

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

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

Reserved for future use; sometimes used by APIs requiring payment.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

The HTTP method used is not supported for this resource.

The server cannot produce a response matching the client's Accept headers.

The client must authenticate with a proxy before the request can proceed.

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

The request conflicts with the current state of the target resource.

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

The server requires a Content-Length header but the client did not send one.

A precondition specified in the request headers was not met.

The request body is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

The request's Content-Type is not supported by the server for this resource.

The requested byte range cannot be satisfied.

The server cannot meet the requirements of the Expect header.

Returned by teapots requested to brew coffee. (April Fools' joke from RFC 2324.)

The request was well-formed but contains semantic errors that prevent processing.

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

The client must switch to a different protocol to complete the request.

The 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 resource is unavailable due to legal demands (censorship, court order, GDPR).

Nginx-specific code: the client closed the connection before the server could respond.

A generic server-side error — the server encountered an unexpected condition.

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

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

The server is temporarily unable to handle the request (overload or maintenance).

The gateway/proxy did not receive a timely response from the upstream server.

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

The server cannot store the representation needed to complete the request.

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 must authenticate to gain network access (e.g., captive portals).