Códigos de Estado HTTP

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

Authentication is required and has failed or not been provided.

Reserved for future use (often used for digital payment systems).

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 server cannot produce a response matching the list of acceptable values defined in the request.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

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

The requested resource is no longer available at the server.

The request did not specify the length of its content, which is required.

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

The request is larger than the server is willing 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 range specified in the request header cannot be fulfilled.

The expectation given in the Expect request header could not be met.

The server refuses to brew coffee because it is a teapot (April Fools' joke from 1998).

The request was directed at a server that cannot produce a response.

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

The resource is locked and cannot be accessed.

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

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.

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

The resource is unavailable for legal reasons.