Hoja de trucos y referencia de códigos de estado HTTP

Initial part of a request has been received and the client should proceed with the request.

Server is switching protocols according to Upgrade request header (e.g. WebSockets).

Standard response for successful HTTP requests.

Request succeeded and a new resource was created (typically after POST/PUT).

Server successfully fulfilled request and there is no additional content to send in response payload.

Target resource has been assigned a new permanent URI. Search engines transfer SEO link juice.

Target resource resides temporarily under a different URI.

Client can use cached version of requested resource (ETag / If-Modified-Since match).

Target resource has been assigned a new permanent URI and request method must NOT change.

Server cannot process request due to perceived client error (malformed syntax, invalid JSON).

Request requires user authentication (valid Bearer token or credentials).

Server understood request but refuses to authorize it (insufficient permissions).

Origin server did not find a current representation for target resource.

Request method is known by server but not supported by target resource (e.g. POST to a GET route).

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

Server encountered an unexpected condition that prevented it from fulfilling request.

Server acting as a gateway or proxy received an invalid response from inbound server.

Server is currently unable to handle request due to temporary overload or scheduled maintenance.

Server acting as gateway did not receive a timely response from upstream server.