Codes de statut HTTP

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.

Used to return some response headers before the final HTTP message so the browser can start preloading resources.

Standard response for a successful HTTP request.

The request succeeded and a new resource was created.

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

The returned metadata originated from a local or third-party copy rather than the origin server.

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

The server asks the client to reset the document view that sent the request.

The server is delivering only part of the resource because the client requested a byte range.

WebDAV: conveys information about multiple resources in a single XML response.

WebDAV: the members of a DAV binding have already been enumerated in a previous reply.

The server fulfilled a GET request using an instance-manipulation applied to the current instance.

The request has more than one possible response; the user agent can choose among them.

This and all future requests should be directed to the given URL.

The resource resides temporarily under a different URL; the method may be changed to GET.

The response to the request can be found under another URI using a GET request.

The resource has not been modified since the version specified by the request headers.

The requested resource is available only through a proxy (deprecated).

No longer used; originally meant subsequent requests should use a specified proxy.

The request should be repeated with another URL; the request method must not change.

This and all future requests should use another URL; the request method must not change.

The server cannot process the request due to a client error such as malformed syntax.

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

Reserved for future use; sometimes used for paywalled resources.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

The request method is not supported for the requested resource.

The requested resource can only generate content not acceptable per the Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the client to send the request.

The request could not be processed because of a conflict with the current state of the resource.

The 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 resource.

The server does not meet one of the preconditions given in the request headers.

The request payload is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

The request uses a media type the server does not support for the resource.

The portion of the resource requested in the Range header cannot be supplied by the server.

The server cannot meet the requirements of the Expect request header field.

RFC 2324 joke status: the server refuses to brew coffee because it is, permanently, a teapot.

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

The server understands the content type and syntax but cannot process the contained instructions (WebDAV).

WebDAV: the source or destination resource of the method is locked.

WebDAV: the method could not be performed because the requested action depended on another action that failed.

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

The origin server requires the request to be conditional.

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

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

The resource is unavailable due to legal demands such as government censorship or a takedown.

A generic error message: the server encountered an unexpected condition.

The server does not support the functionality required to fulfill the request.

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

The server is currently unavailable, typically because it is overloaded or down for maintenance.

The server, acting as a gateway, timed out waiting for an upstream response.

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

Transparent content negotiation for the request resulted 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 must authenticate to gain network access, as with a captive portal.