Referencia de Códigos de Estado HTTP

Continue

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

Switching Protocols

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

Processing

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

Early Hints

Used to return some response headers before the final HTTP message, allowing the client to preload resources.

OK

The request succeeded. The response body contains the requested data.

Created

The request succeeded and a new resource was created. Typically returned after POST or PUT requests.

Accepted

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

No Content

The request succeeded but there is no content to send in the response body.

Partial Content

The server delivers only part of the resource due to a range header sent by the client.

Multi-Status

Conveys information about multiple resources, used in WebDAV when the response may contain multiple status codes.

Moved Permanently

The requested resource has been permanently moved to a new URL. Clients should update their bookmarks.

Found

The resource is temporarily at a different URL. The client should continue using the original URL for future requests.

See Other

The server directs the client to get the requested resource at another URL using a GET request.

Not Modified

The resource has not been modified since the last request. The client can use the cached version.

Temporary Redirect

The resource is temporarily at a different URL. Unlike 302, the request method must not change.

Permanent Redirect

The resource has permanently moved to a new URL and the request method must not change.

Bad Request

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

Unauthorized

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

Forbidden

The server understood the request but refuses to authorize it. Authentication will not help.

Not Found

The server cannot find the requested resource. The URL is not recognized or the resource does not exist.

Method Not Allowed

The HTTP method used in the request is not allowed for the target resource.

Request Timeout

The server timed out waiting for the request. The client may repeat the request without modification.

Conflict

The request conflicts with the current state of the target resource.

Gone

The resource is no longer available and no forwarding address is known. This condition is expected to be permanent.

Content Too Large

The request body is larger than the limits defined by the server.

Unsupported Media Type

The media format of the requested data is not supported by the server.

Unprocessable Entity

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

Too Many Requests

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

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

Not Implemented

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

Bad Gateway

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

Service Unavailable

The server is not ready to handle the request. Common causes are overloading or maintenance.

Gateway Timeout

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

HTTP Version Not Supported

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