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

A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.

Used to return some response headers before final HTTP message.

The request is successful. The meaning of success 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 the processing has not been completed.

The request was successful but the information may have been modified by a transforming proxy.

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

The server successfully processed the request but is not returning any content and 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.

Provides status for multiple independent operations.

The members of a DAV binding have already been enumerated in a preceding part of the multistatus response.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

The request has more than one possible response. The user agent should choose one of them.

The URL of the requested resource has been changed permanently. The new URL is given in the response.

The URL of the requested resource has been changed temporarily. Further changes in the URL might be made in the future.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

Used for caching purposes. The client can use cached version of the response.

The requested resource is available only through a proxy.

This response code is no longer used and is reserved.

The server sends this response to direct the client to get the requested resource at another URI with the same method.

This means the resource is now permanently located at another URI.

The server could not understand the request due to invalid syntax.

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

This response code is reserved for future use and was originally created for digital payment systems.

The client does not have access rights to the content; the server is refusing to give the requested resource.

The server can not find the requested resource. This is the most common error on the internet.

The request method is known by the server but is not supported by the target resource.

The server cannot produce a response matching the list of acceptable values defined in the request's headers.

This is similar to 401 but authentication is required to be done by a proxy.

The server timed out waiting for the request. The client did not produce a request within the time the server was prepared to wait.

This response is sent when a request conflicts with the current state of the server.

The requested content has been permanently deleted from the server with no forwarding address.

The server rejects the request because the Content-Length header field is not defined and the server requires it.

The client has indicated preconditions in its headers which the server does not meet.

The request entity is larger than limits defined by the 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 field in the request cannot be fulfilled.

The expectation indicated by the Expect request header field cannot be met by the server.

This code was defined in 1998 as one of the traditional IETF April Fools' jokes.

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

The request was well-formed but was unable to be followed due to semantic errors.

The resource that is being accessed is locked.

The request failed because it depended on another request and that request failed.

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

The server refuses to perform the request using the current protocol.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time.

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

The server is denying access to the resource as a consequence of a legal demand.

The server has encountered a situation it does not know how to handle.

The request method is not supported by the server and cannot be handled.

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

The server is not ready to handle the request. Common causes are a server that is down for maintenance or is overloaded.

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error.

The method could not be performed on the resource because the server is unable to store the representation needed to successfully 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.