Códigos de status HTTP

The client should continue with its request; the initial part was received.

The server is switching protocols as requested by the client (e.g. to WebSocket).

The server has accepted the request but has not yet completed it (WebDAV).

Returns preliminary headers (e.g. Link) so the client can begin preloading.

Standard success response; the meaning depends on the HTTP method used.

The request succeeded and a new resource was created.

The request was accepted for processing but is not yet complete.

Returned metadata came from a copy, not the origin server.

The request succeeded but there is no body to return.

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

The server is delivering only part of the resource due to a Range header.

Conveys multiple independent status codes for a WebDAV request.

Members of a WebDAV binding were already enumerated and are not repeated.

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

The request has more than one possible response; the client should choose.

The resource moved permanently to a new URL; update links to it.

The resource is temporarily at a different URL; keep using the original.

Fetch the resource at another URI with a GET request.

The cached version is still valid; the client can reuse it.

Like 302 but the method and body must not change on the redirect.

Like 301 but the method and body must not change on the redirect.

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

Authentication is required and has failed or not been provided.

Reserved for future use; sometimes used by APIs for rate or quota limits.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource.

The HTTP method is not supported for the target resource.

No representation matches the request’s Accept headers.

The client must authenticate with a proxy first.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

The resource is permanently gone and no forwarding address is known.

The request must include a Content-Length header.

A precondition in the request headers evaluated to false.

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

The requested URI is longer than the server will interpret.

The request’s media type is not supported by the resource.

The requested Range cannot be served.

The Expect request header could not be met.

An April Fools’ joke code (RFC 2324); the server refuses to brew coffee.

The request was directed at a server unable to produce a response.

The request was well-formed but had semantic errors (WebDAV / APIs).

The resource being accessed is locked (WebDAV).

The request failed because a previous request it depended on failed.

The server is unwilling to risk processing a possibly replayed request.

The client should switch to a different protocol given in the Upgrade header.

The origin server requires the request to be conditional.

The client has sent too many requests in a given time (rate limiting).

The headers are too large for the server to process.

The resource is unavailable due to legal demands.

A generic error; the server hit an unexpected condition.

The server does not support the functionality to fulfil the request.

A gateway or proxy received an invalid response from the upstream server.

The server is temporarily overloaded or down for maintenance.

A gateway or proxy did not get a timely response from the upstream server.

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

A content-negotiation configuration error on the server.

The server cannot store the representation needed to complete the request (WebDAV).

The server detected an infinite loop while processing the request (WebDAV).

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

The client must authenticate to gain network access (e.g. captive portals).