HTTP Status Codes Wall

Continue

The initial part of a request has been received and the client can proceed with the request body.

Switching Protocols

The server is switching protocols as requested by the client, typically to WebSocket.

Processing

WebDAV: the server has received and is processing the request, but no response is available yet.

Early Hints

The server sends preliminary response headers before the final response, typically Link headers for resource preloading.

OK

The request succeeded. The response body contains the requested representation.

Created

A new resource has been created as a result of the request. The URI of the new resource is in the Location header.

Accepted

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

No Content

The request succeeded, and there is no additional content to send in the response body.

Reset Content

The server has fulfilled the request and asks the user agent to reset the view (e.g. clear a form).

Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

Moved Permanently

The resource has been permanently moved to a new URL. Clients and search engines should update their references.

Found

The resource is temporarily at a different URL. The client should continue to use the original URL for future requests.

See Other

The response to the request can be found under a different URL, and the client should perform a GET to that URL.

Not Modified

The cached copy the client already has is still valid; no body is returned.

Temporary Redirect

Like 302 but explicitly preserves the request method (POST stays POST, etc.).

Permanent Redirect

Like 301 but explicitly preserves the request method.

Bad Request

The server cannot process the request due to a client error (malformed syntax, invalid framing, etc.).

Unauthorized

Authentication is required and has not been provided, or provided credentials are invalid.

Forbidden

The server understood the request and the client is authenticated, but access is refused.

Not Found

The server has not found anything matching the requested URL.

Method Not Allowed

The HTTP method is known but not supported for this specific URL.

Not Acceptable

The server cannot produce a response matching the Accept headers sent by the client.

Request Timeout

The server did not receive a complete request within the time it was prepared to wait.

Conflict

The request conflicts with the current state of the resource.

Gone

The resource is no longer available and has been permanently removed.

Length Required

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

Precondition Failed

A precondition given in the request headers (e.g. If-Match) evaluated to false.

Payload Too Large

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

URI Too Long

The URL exceeds the maximum length the server is willing to process.

Unsupported Media Type

The server refuses to process the request because the payload format is unsupported.

I'm a teapot

The server refuses to brew coffee because it is, permanently, a teapot.

Unprocessable Entity

The request is well-formed but contains semantic errors and cannot be processed.

Too Early

The server is unwilling to risk processing a request that might be replayed (used with TLS 0-RTT).

Precondition Required

The server requires the request to be conditional (e.g. include If-Match).

Too Many Requests

The client has sent too many requests in a given amount of time (rate limited).

Request Header Fields Too Large

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

Unavailable For Legal Reasons

The resource is unavailable due to legal demands (censorship, DMCA, GDPR).

Internal Server Error

A generic error message given when an unexpected condition was encountered on the server.

Not Implemented

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

Bad Gateway

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

Service Unavailable

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

Gateway Timeout

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

HTTP Version Not Supported

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

Insufficient Storage

WebDAV: the server is unable to store the representation needed to complete the request.

Loop Detected

WebDAV: the server detected an infinite loop while processing the request.

Network Authentication Required

The client needs to authenticate to gain network access (e.g. captive portal at a Wi-Fi hotspot).