HTTP Status Code Reference
Searchable reference for all HTTP status codes with descriptions. Filter by category or search by code/name.
The server has received the request headers, and the client should proceed to send the request body.
The server is switching protocols as requested by the client (e.g., upgrading to WebSocket).
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message. Allows preloading resources.
The request has succeeded. The meaning depends on the HTTP method used.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but processing is not yet complete.
The returned metadata is from a local or third-party copy, not the origin server.
The server successfully processed the request, but is not returning any content.
The server successfully processed the request and asks the client to reset the document view.
The server is delivering only part of the resource due to a Range header sent by the client.
The message body contains multiple separate response codes (WebDAV).
Members of a DAV binding have already been reported; not included again.
Multiple options for the resource exist, and the user or agent can select.
The resource has been permanently moved to a new URL. Future requests should use the new URL.
The resource is temporarily located at a different URL. Continue using the original URL.
The response can be found at another URL using a GET request.
The resource has not been modified since last requested. Use cached version.
The resource is temporarily at a different URL. Method and body must not change.
The resource has permanently moved. Method and body must not change.
The server cannot process the request due to malformed syntax or invalid parameters.
Authentication is required. The client must authenticate to get the requested response.
Reserved for future use. Sometimes used for digital payment systems.
The server understood the request but refuses to authorize it. Authentication won't help.
The server cannot find the requested resource. The URL is not recognized.
The HTTP method used is not supported for this resource.
The server cannot produce a response matching the Accept headers sent.
The client must authenticate with the proxy before the request can proceed.
The server timed out waiting for the client to send the request.
The request conflicts with the current state of the resource (e.g., edit conflicts).
The resource is no longer available and will not be available again. Permanently deleted.
The server requires a Content-Length header in the request.
A precondition in the request headers was evaluated as false by the server.
The request body is larger than the server is willing or able to process.
The request URI is longer than the server is willing to interpret.
The media type of the request body is not supported by the server.
The range specified in the Range header cannot be fulfilled.
The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324).
The request was well-formed but semantically incorrect (validation errors).
The resource is currently locked (WebDAV).
The server is unwilling to process a request that might be replayed.
The client should switch to a different protocol (e.g., TLS/1.0).
The server requires the request to be conditional (If-Match, etc.).
The user has sent too many requests in a given time (rate limiting).
The server refuses the request because headers are too large.
The resource is unavailable due to legal demands (censorship, DMCA).
A generic error when the server encounters an unexpected condition.
The server does not support the functionality required to fulfill the request.
The server received an invalid response from an upstream server.
The server is temporarily unable to handle the request (maintenance, overload).
The server did not receive a timely response from an upstream server.
The server does not support the HTTP version used in the request.
The server cannot store the representation needed to complete the request.
The server detected an infinite loop while processing the request.
The client needs to authenticate to gain network access (captive portals).