Busca de Código de Status HTTP

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

The server is switching protocols as requested by the client — typically HTTP to WebSocket.

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

Returns some response headers before the final response to allow the client to start preloading resources.

The request was successful. The response body contains the requested data.

The request was successful and a new resource was created. The Location header typically points to the new resource.

The request was accepted for processing but processing has not been completed — it may not be completed.

The response is from a proxy that modified the original server's 200 response.

The request was successful but there is no content to return. Used for DELETE or updates.

The server processed the request and the client should reset the document view (e.g., clear a form).

The server is delivering a portion of the resource (partial response) due to a Range request header.

Contains information about multiple resources in situations where multiple status codes might be appropriate (WebDAV).

The members of a DAV binding have already been enumerated in a previous reply and are not included again.

The server fulfilled a GET request for the resource and the response is a representation of the result of one or more instance-manipulations.

The request has multiple possible responses. The client should choose one.

The resource has permanently moved to a new URL. Clients and search engines should update their bookmarks.

The resource is temporarily at a different URL. Clients should continue using the original URL in the future.

The response to the request can be found at a different URL using a GET request (PRG pattern).

The resource has not been modified since the version specified in the request headers. Use cached version.

Same as 302 but explicitly requires the same HTTP method to be used on the redirect.

Same as 301 but explicitly requires the same HTTP method to be used on the redirect.

The server cannot process the request due to malformed syntax, invalid parameters, or missing required data.

The request requires authentication. The client must provide valid credentials.

Reserved for future use. Some APIs use it to indicate payment is needed.

The server understood the request but refuses to authorize it. Authentication won't help.

The server cannot find the requested resource. The URL may be wrong or the resource deleted.

The HTTP method used is not allowed for this endpoint.

The server cannot produce a response matching the Accept headers sent by the client.

The client must authenticate with a proxy before proceeding.

The server timed out waiting for the request to complete.

The request conflicts with the current state of the server (e.g., duplicate resource, version conflict).

The resource was permanently deleted and will not be available again. Unlike 404, this is intentional.

The server requires a Content-Length header for this request.

A precondition in the request headers was not met (e.g., If-Match or If-Unmodified-Since).

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

The URL is longer than the server can process.

The server does not support the Content-Type of the request body.

The Range header cannot be fulfilled — the range is outside the resource size.

The server cannot meet the requirements of the Expect request header.

An April Fools' joke from RFC 2324 (Hyper Text Coffee Pot Control Protocol). Some servers use it for joke responses or to block bots.

The request was well-formed but failed semantic validation. Often returned with validation errors.

The resource is locked (WebDAV). Another operation has the resource locked.

The request failed because it depended on another request that failed (WebDAV).

The server is unwilling to process a request that might be replayed (TLS 0-RTT anti-replay).

The server requires the client to upgrade to a different protocol.

The server requires the request to be conditional (use If-Match or similar headers).

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

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

The resource is unavailable due to legal reasons such as censorship or GDPR compliance.

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

The server does not recognize or cannot implement the request method.

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

The server is temporarily unable to handle the request — overloaded or under maintenance.

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

The server does not support the HTTP version used in the request.

The server cannot store the representation needed to complete the request (WebDAV).

The server detected an infinite loop while processing a request (WebDAV).

The server requires further extensions for the request to be fulfilled.

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