HTTP Statuscode Referenz

Continue

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

Switching Protocols

The server agrees to switch protocols as requested by the client via the Upgrade header.

Processing

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

Early Hints

Used to return response headers before the final HTTP message, allowing the browser to start preloading resources.

Accepted

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

Non-Authoritative Information

The request succeeded but the returned metadata is from a local or third-party copy, not the origin server.

No Content

The request succeeded but there is no content to return. Common for DELETE or PATCH API responses.

Reset Content

The server fulfilled the request and asks the client to reset the document view (e.g., clear a form).

Partial Content

The server is delivering only part of the resource due to a Range header. Used in streaming and resumable downloads.

Multi-Status

Conveys information about multiple resources in situations where multiple status codes might be appropriate. Used in WebDAV.

Already Reported

The members of a DAV binding have already been enumerated in a preceding part of the response.

IM Used

The server fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations.

Multiple Choices

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

See Other

The server redirects the client to a different resource using a GET request. Often used after a POST to prevent form resubmission.

Temporary Redirect

Like 302, but explicitly preserves the HTTP method. Use when method preservation is required for temporary redirects.

Permanent Redirect

Like 301, but preserves the HTTP method. Used in APIs that need to permanently redirect POST requests.

Payment Required

Reserved for future use. Originally intended for digital payment systems; now used by some APIs to signal quota limits.

Method Not Allowed

The HTTP method used is not allowed for the requested resource. The response must include an Allow header listing valid methods.

Not Acceptable

The server cannot produce a response matching the list of acceptable values in the request's Accept headers.

Proxy Authentication Required

Authentication with the proxy server is required before the request can be fulfilled.

Request Timeout

The server timed out waiting for the request. The client may repeat the request without modifications.

Conflict

The request conflicts with the current state of the target resource. Common when trying to create a duplicate record.

Length Required

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

Precondition Failed

The server does not meet one or more preconditions set in the request headers.

Content Too Large

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

URI Too Long

The URI requested by the client is longer than the server is willing to interpret.

Unsupported Media Type

The media format of the requested data is not supported by the server. Check the Content-Type header.

Range Not Satisfiable

The server cannot serve the requested ranges. The Range header field value is outside the resource's actual size.

Expectation Failed

The server cannot meet the expectations indicated by the Expect request-header field.

I'm a Teapot

The server refuses to brew coffee because it is, permanently, a teapot. An April Fools' joke from RFC 2324 (1998), now a web easter egg.

Misdirected Request

The request was directed at a server that is not able to produce a response for the combination of scheme and authority.

Unprocessable Content

The request is syntactically valid but semantically incorrect. Common in REST APIs with strict field validation.

Locked

The resource being accessed is locked. Used in WebDAV to indicate the resource is locked.

Failed Dependency

The request failed because it depended on another request that failed. Used in WebDAV.

Too Early

The server is unwilling to risk processing a request that might be replayed, to prevent replay attacks.

Upgrade Required

The client should switch to a different protocol. The server sends an Upgrade header indicating the required protocol.

Precondition Required

The origin server requires the request to be conditional. Prevents the "lost update" problem in REST APIs.

Request Header Fields Too Large

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

Unavailable For Legal Reasons

The server cannot legally provide the requested resource. Named after Fahrenheit 451. Used for censorship or legal blocks.

Not Implemented

The server does not support the functionality required to fulfill the request. The method is not recognized or implemented.

HTTP Version Not Supported

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

Variant Also Negotiates

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

Insufficient Storage

The server cannot store the representation needed to complete the request. Used in WebDAV.

Loop Detected

The server detected an infinite loop while processing the request. Used in WebDAV.

Not Extended

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

Network Authentication Required

The client needs to authenticate to gain network access. Used by captive portals (hotel Wi-Fi, etc.) to intercept HTTP requests.