Continue
Initial part of a request was received and the client should continue with it.
Códigos de estado HTTP
Referência pesquisável de códigos de estado HTTP com descrições e referências a RFCs.
62 mostrados
1xxInformational · 4
RFC 9110
Switching Protocols
Server agrees to switch protocols based on the Upgrade header.
Processing
Server has accepted the request but is still processing it (WebDAV).
Early Hints
Send preliminary headers (Link, etc.) before the final response.
2xxSuccess · 10
OK
Request succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request was accepted for processing but has not yet completed.
Non-Authoritative Information
Returned metainformation differs from the origin server's response.
No Content
Request succeeded; no body to return.
Reset Content
Request succeeded; the client should reset the document view.
Partial Content
Range request succeeded.
Multi-Status
Body is an XML message with status for multiple resources (WebDAV).
Already Reported
Members of a WebDAV binding were already enumerated.
IM Used
Server fulfilled a GET request and the response is a representation of one or more instance manipulations.
3xxRedirection · 8
Multiple Choices
Multiple representations are available; the client may choose.
Moved Permanently
Resource has a new permanent URI.
Found
Resource is temporarily under a different URI.
See Other
Response is found under a different URI; client should GET it.
Not Modified
Conditional GET: the cached representation is still fresh.
Use Proxy
Deprecated. Resource must be accessed through a proxy.
Temporary Redirect
Resource is temporarily under a different URI; method must not change.
Permanent Redirect
Resource has a new permanent URI; method must not change.
4xxClient error · 29
Bad Request
Server cannot or will not process the request due to a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
Server can't find the requested resource.
Method Not Allowed
Method is known but not supported by the target resource.
Not Acceptable
Resource cannot generate content matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy first.
Request Timeout
Server timed out waiting for the client.
Conflict
Request conflicts with the current state of the resource.
Gone
Resource is permanently unavailable.
Length Required
Server requires the Content-Length header.
Precondition Failed
Precondition in request headers failed.
Content Too Large
Request body is larger than the server is willing to process.
URI Too Long
Request URI is longer than the server is willing to interpret.
Unsupported Media Type
Request body is in a format the server doesn't support.
Range Not Satisfiable
None of the ranges in the Range header overlap the resource.
Expectation Failed
Expectation in the Expect header could not be met.
I'm a teapot
Server is a teapot. April Fools' joke from RFC 2324; widely implemented as an Easter egg.
Misdirected Request
Request was directed to a server unable to produce a response.
Unprocessable Content
Request is well-formed but semantically invalid.
Locked
Resource is locked (WebDAV).
Failed Dependency
Request failed because of a previous request (WebDAV).
Too Early
Server is unwilling to risk processing a request that might be replayed.
Upgrade Required
Client must switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time (rate limited).
Request Header Fields Too Large
One or more request headers (or all of them) are too large.
Unavailable For Legal Reasons
Resource is unavailable due to legal demands.
5xxServer error · 11
Internal Server Error
Server encountered an unexpected condition.
Not Implemented
Server does not support the functionality required.
Bad Gateway
Server, while acting as a gateway, got an invalid response from upstream.
Service Unavailable
Server is currently unable to handle the request (overloaded or down).
Gateway Timeout
Server, while acting as a gateway, didn't get a response in time.
HTTP Version Not Supported
Server doesn't support the HTTP version in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
Server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
Server detected an infinite loop while processing (WebDAV).
Not Extended
Further extensions to the request are required.
Network Authentication Required
Client needs to authenticate to gain network access (captive portal).
As entradas ficam neste dispositivo. Cada ferramenta para programadores no TaskKit corre inteiramente no teu navegador. Tokens, payloads e texto colado não são transmitidos para servidores do TaskKit nem para terceiros.
O que esta ferramenta faz
Uma referência pesquisável para cada código de estado HTTP padrão, organizada por classe (1xx informacional, 2xx sucesso, 3xx redirecionamento, 4xx erro do cliente, 5xx erro do servidor). Pesquisa por número, por nome ou por descrição. Cada entrada inclui a frase de razão canónica e o RFC onde está definida.
Quando usar
- Decidir entre
401 Unauthorizede403 Forbiddenpara um pedido recusado. - Confirmar se um redirecionamento deve ser
302,303,307ou308. - Pesquisar um código desconhecido que apareceu agora numa linha de log.
- Verificar que RFC introduziu um código (por exemplo,
451 Unavailable For Legal Reasonsé o RFC 7725).
Como funciona
O conjunto de dados é estático e vem no bundle da página. Não há chamada de API — a pesquisa corre contra um índice em memória, por isso é instantânea mesmo em ligações lentas. Os metadados de cada código vêm diretamente do IANA HTTP Status Code Registry e dos RFCs relevantes (sobretudo o 9110, com códigos mais antigos a apontar para o 7231 e anteriores).
Notas
401 vs 403? 401 significa "não provaste quem és — tenta de novo com credenciais". 403 significa "sei quem és e não podes ter isto". Se o utilizador autenticar-se mudaria a resposta, devolve 401; se não, 403.
302 vs 307? O 302 foi originalmente pensado para preservar o método do pedido no redirecionamento, mas a maioria dos navegadores historicamente reescreveu POST como GET. 303 e 307 foram acrescentados para tornar a intenção explícita: 303 See Other faz sempre GET ao novo URL, 307 Temporary Redirect preserva sempre o método. Usa 303 depois de um POST bem-sucedido, 307 para um redirecionamento temporário que preserva o método.
418 I'm a teapot é a sério? Sim, e ainda está no RFC 2324 (1 de abril de 1998) e reconhecido no RFC 9110 §15.5.19. Usa com moderação.
Ferramentas relacionadas
- cURL ↔ fetch — replica pedidos para ver os códigos ao vivo
- Formatador JSON — para inspecionar corpos de resposta