Códigos de estado HTTP

The initial part of the request has been received; the client should continue.

The server is switching to a different protocol as requested by the client.

Used with Link header to preload resources before final response.

Standard successful response.

The request succeeded and a new resource was created.

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

Request succeeded with no response body.

Response contains a partial range of the resource (used for range requests).

The resource has permanently moved to a new URL.

The resource is temporarily located at a different URL.

Cached version is still valid; body is not sent.

Same method must be used for the redirected request.

Permanent redirect; method must not change.

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

Authentication is required and has failed or not been provided.

The server understood the request but refuses to authorize it.

The requested resource could not be found.

The HTTP method is not supported for this resource.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

The resource has been permanently removed.

Request entity exceeds server-defined limits.

The media type of the request data is not supported.

An April Fools' RFC joke — the server refuses to brew coffee.

The request was well-formed but semantically invalid.

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

Content blocked for legal reasons.

A generic server-side error occurred.

The server does not support the request method.

The server received an invalid response from an upstream server.

The server is temporarily unavailable, usually due to maintenance or overload.

An upstream server did not respond in time.

The client must authenticate to gain network access (captive portal).