HTTP status code list

ContinueNo body

The request headers were accepted; the client should continue sending the body.

RFC 9110 §15.2.1

Switching ProtocolsNo body

Switching to the protocol requested in Upgrade, as used by the WebSocket handshake.

RFC 9110 §15.2.2

ProcessingNo body

An interim response signalling that the server is still processing, used by WebDAV.

RFC 2518 §10.1

Early HintsNo body

Sends Link headers ahead of the final response so the client can preload.

RFC 8297 §2

OK

The request succeeded; for GET the body is the representation itself.

RFC 9110 §15.3.1

Created

A new resource was created; its URI belongs in the Location header.

RFC 9110 §15.3.2

Accepted

The request was accepted but not yet processed, as with an asynchronous job.

RFC 9110 §15.3.3

Non-Authoritative Information

The payload was modified by a proxy rather than coming straight from the origin.

RFC 9110 §15.3.4

No ContentNo body

Success with no body, a good fit for DELETE and for saving a form.

RFC 9110 §15.3.5

Reset ContentNo body

Success; the client should reset the document view that sent the request.

RFC 9110 §15.3.6

Partial Content

A range request was fulfilled with part of the representation, as in resumable transfers.

RFC 9110 §15.3.7

Multi-Status

Per-resource results are returned in an XML body, used by WebDAV.

RFC 4918 §11.1

Already Reported

Members of a binding were already enumerated earlier in the response, used by WebDAV.

RFC 5842 §7.1

IM Used

The response is the result of one or more instance manipulations applied to the resource.

RFC 3229 §10.4.1

Multiple Choices

More than one representation exists and the client should choose.

RFC 9110 §15.4.1

Moved Permanently

Permanently moved; most clients rewrite the follow-up POST into a GET.

RFC 9110 §15.4.2

Found

Temporarily located elsewhere; method preservation is not guaranteed, so prefer 307.

RFC 9110 §15.4.3

See Other

Fetch the result with GET, the redirect behind the post/redirect/get pattern.

RFC 9110 §15.4.4

Not ModifiedNo body

The cached representation is still fresh for this conditional request.

RFC 9110 §15.4.5

Temporary Redirect

A temporary redirect that preserves the method and body.

RFC 9110 §15.4.8

Permanent Redirect

A permanent redirect that preserves the method and body.

RFC 9110 §15.4.9

Bad Request

The server cannot process the request because it is malformed.

RFC 9110 §15.5.1

Unauthorized

Authentication is required or failed; WWW-Authenticate is mandatory.

RFC 9110 §15.5.2

Payment Required

Reserved for future use.

RFC 9110 §15.5.3

Forbidden

Authenticated but not permitted; return 404 instead when hiding existence matters.

RFC 9110 §15.5.4

Not Found

The resource was not found, also used to avoid disclosing that it exists.

RFC 9110 §15.5.5

Method Not Allowed

The method is not allowed for this resource; the Allow header is mandatory.

RFC 9110 §15.5.6

Not Acceptable

No representation matches the request Accept headers.

RFC 9110 §15.5.7

Proxy Authentication Required

The client must authenticate with the proxy first.

RFC 9110 §15.5.8

Request Timeout

The client did not produce a complete request in time.

RFC 9110 §15.5.9

Conflict

The request conflicts with the current state, such as an optimistic-locking clash.

RFC 9110 §15.5.10

Gone

Permanently removed; unlike 404 it states the resource will not come back.

RFC 9110 §15.5.11

Length Required

The request must include a Content-Length header.

RFC 9110 §15.5.12

Precondition Failed

A precondition such as If-Match evaluated to false.

RFC 9110 §15.5.13

Content Too Large

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

RFC 9110 §15.5.14

URI Too Long

The request URI is longer than the server will interpret.

RFC 9110 §15.5.15

Unsupported Media Type

The payload media type is not supported.

RFC 9110 §15.5.16

Range Not Satisfiable

The requested range lies outside the representation.

RFC 9110 §15.5.17

Expectation Failed

The expectation in the Expect header could not be met.

RFC 9110 §15.5.18

I'm a Teapot

An April Fools joke specification; do not use it in production.

RFC 2324 §2.3.2

Misdirected Request

The request went to a server unable to answer for that authority, seen with HTTP/2 coalescing.

RFC 9110 §15.5.20

Unprocessable Content

Syntactically valid but semantically wrong, the usual choice for validation errors.

RFC 9110 §15.5.21

Locked

The resource is locked, used by WebDAV.

RFC 4918 §11.3

Failed Dependency

A dependent request failed, used by WebDAV.

RFC 4918 §11.4

Too Early

The server will not process early data that risks replay, as with TLS 1.3 0-RTT.

RFC 8470 §5.2

Upgrade Required

The client must switch to a different protocol.

RFC 9110 §15.5.22

Precondition Required

Requires a conditional request so concurrent updates cannot be lost.

RFC 6585 §3

Too Many Requests

The client hit a rate limit; pair it with a Retry-After header.

RFC 6585 §4

Request Header Fields Too Large

The header fields are too large, often from oversized cookies.

RFC 6585 §5

Unavailable For Legal Reasons

The resource is unavailable for legal reasons.

RFC 7725 §3

Internal Server Error

An unexpected server-side failure; keep the details out of the response.

RFC 9110 §15.6.1

Not Implemented

The server does not implement the requested method.

RFC 9110 §15.6.2

Bad Gateway

An invalid response came back from an upstream server.

RFC 9110 §15.6.3

Service Unavailable

Temporarily unable to handle the request; pair it with Retry-After.

RFC 9110 §15.6.4

Gateway Timeout

No timely response arrived from an upstream server.

RFC 9110 §15.6.5

HTTP Version Not Supported

The requested HTTP version is not supported.

RFC 9110 §15.6.6

Variant Also Negotiates

The server has a content-negotiation configuration error.

RFC 2295 §8.1

Insufficient Storage

There is not enough storage to complete the request, used by WebDAV.

RFC 4918 §11.5

Loop Detected

An infinite loop was detected while processing, used by WebDAV.

RFC 5842 §7.2

Not ExtendedDeprecated

Further extensions to the request are required.

RFC 2774 §7

Network Authentication Required

Network access requires authentication, as behind a captive portal.

RFC 6585 §6