Códigos 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.

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.

The request has succeeded. Standard response for successful HTTP requests.

The request has been fulfilled and a new resource has been created.

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

The returned information is from a local or third-party copy, not from the original server.

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

The server successfully processed the request but is not returning any content. Requires the requester 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 XML with multiple status codes for multiple sub-requests.

The members of a DAV binding have already been enumerated in a previous reply.

The server has fulfilled a GET request for the resource with instance-manipulations applied.

There are multiple options for the resource that the client may follow.

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. Future requests should still use the original URL.

The response to the request can be found under a different URL using a GET method.

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

The request should be repeated with another URL, but future requests should still use the original URL.

The request and all future requests should be repeated using another URL.

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

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

Reserved for future use. Originally intended for digital payment schemes.

The client does not have permission to access the requested resource.

The requested resource could not be found on the server.

The request method is not supported for the requested resource.

The requested resource cannot generate content acceptable according to the Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

The request could not be processed because of conflict in 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 specified in the request headers.

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

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

The request entity has a media type which the server does not support.

The client has asked for a portion of the file that the server cannot supply.

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

The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324).

The request was well-formed but contains semantic errors.

The resource that is being accessed is locked.

The request failed due to failure of a previous request.

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

The client should switch to a different protocol.

The origin server requires the request to be conditional.

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

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

The resource is unavailable due to legal demands (censorship, government-mandated block).

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

The server does not recognize the request method or cannot fulfill the request.

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

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

The server was acting as a gateway or proxy and 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.

The server is unable to store the representation needed to complete the request.

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 (captive portal).