Referencia de HTTP Status Codes

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

The requester has asked the server to switch protocols and the server has agreed to do so.

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

Used to return some response headers before final HTTP message.

Standard response for successful HTTP requests.

The request has been fulfilled, resulting in the creation of a new resource.

The request has been accepted for processing but processing is not complete.

Returned meta-information is from a local or third-party copy.

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

Tells the user agent to reset the document which sent this request.

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

WebDAV — conveys information about multiple resources.

WebDAV — members of a DAV binding have already been enumerated.

The server has fulfilled a GET request using instance manipulations.

The request has multiple possible responses; the user or agent should choose one.

The resource has been permanently moved to a new URL.

The resource is temporarily at a different URL; clients should continue using the original URL.

The response can be found at another URL using a GET method.

The resource has not been modified since the last request. Used for caching.

The resource is temporarily at a different URL; method and body must be preserved.

The resource has been permanently moved; method and body must be preserved (unlike 301).

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

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

Reserved for future use. Rarely used today outside of specific contexts like Stripe.

The request was valid but the server is refusing to respond. Authentication will not help.

The requested resource could not be found on the server.

The request method is not supported for the target resource.

The server cannot produce a response matching the Accept headers of the request.

The client must authenticate itself with the proxy.

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

The request conflicts with the current state of the server (e.g., duplicate resource).

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

The request did not specify the length of its content, which is required by the target resource.

One or more preconditions given in the request headers evaluated to false.

The request entity is larger than limits defined by server.

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

The media format of the requested data is not supported by the server.

The range specified by the Range header cannot be fulfilled.

The expectation indicated by the Expect request header could not be met.

RFC 2324 April Fools' joke. The server refuses to brew coffee because it is a teapot.

The request was directed at a server that is not able to produce a response.

The request was well-formed but contains semantic errors. Commonly used by validation frameworks.

WebDAV — the resource being accessed is locked.

WebDAV — the request failed because it depended on another request that failed.

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

The client should switch to a different protocol such as TLS/1.3.

The origin server requires the request to be conditional to prevent lost updates.

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

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

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

A generic error message when the server encounters an unexpected condition.

The server does not recognize the request method or lacks the ability to fulfill it.

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

The server is currently unavailable (overloaded or down for maintenance).

The server, acting as a gateway, did not receive a timely response from the upstream server.

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

Transparent content negotiation for the request results in a circular reference.

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

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

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

The client needs to authenticate to gain network access.