Gratis en línea HTTP Status Codes

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

The server agrees to switch protocols as requested by the client via the Upgrade header.

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

Used to return preliminary response headers before the final HTTP message, allowing the client to start preloading resources while the server prepares the response.

The request was successful.

The request was fulfilled and resulted in a new resource being created.

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

The request was successful but the metadata has been modified by a transforming proxy from the origin server's 200 OK response.

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

The server successfully processed the request and tells the client to reset the document view.

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

Conveys information about multiple resources in a single response.

Used inside a DAV binding to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.

The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations applied to the current instance (HTTP Delta encoding).

The request has more than one possible response.

The requested URL has been permanently moved to a new location specified in the Location header.

The requested URL has been temporarily moved.

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

The client's cached version of the resource is still valid.

Deprecated.

The request should be repeated at the URI specified in the Location header using the same method and body.

The request and all future requests should be repeated using the URI specified in the Location header with the same method and body.

The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.

Authentication is required and has failed or not been provided.

Reserved for future use.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource.

The HTTP method used is not allowed for the requested resource.

The server cannot produce a response matching the list of acceptable values specified in the request's proactive content negotiation headers (Accept, Accept-Encoding, Accept-Language).

Similar to 401, but authentication is required by a proxy server standing between the client and the origin server.

The server timed out waiting for the request.

The request could not be completed due to a conflict with the current state of the target resource.

The resource is no longer available and no forwarding address is known.

The server refuses to accept the request without a defined Content-Length header.

One or more conditions given in the request header fields evaluated to false on the server.

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

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 in the Range request header cannot be fulfilled.

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

The server refuses the attempt to brew coffee with 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 that prevent processing.

The source or destination resource of a method is locked.

The method could not be performed on the resource because the requested action depended on another action that failed.

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

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol specified in the Upgrade header.

The origin server requires the request to be conditional.

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

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, such as a government-issued takedown notice or a court order.

A generic error response when the server encounters an unexpected condition that prevents it from fulfilling the request.

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

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, typically due to being overloaded or down for maintenance.

The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.

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

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.