Continue
Initial part of a request was received and the client should continue with it.
Códigos de estado HTTP
Referencia buscable de códigos de estado HTTP con descripciones y referencias 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).
Las entradas se quedan en este dispositivo. Cada herramienta para desarrolladores en TaskKit corre por completo en tu navegador. Tokens, payloads y texto pegado no se transmiten ni a TaskKit ni a terceros.
Qué hace esta herramienta
Referencia buscable de todos los códigos de estado HTTP, desde 100 Continue hasta 599. Busca por código (418), por nombre (teapot) o por descripción. Filtra por categoría:
- 1xx Informativos —
100 Continue,101 Switching Protocols,103 Early Hints... - 2xx Éxito —
200 OK,201 Created,204 No Content,206 Partial Content... - 3xx Redirección —
301 Moved Permanently,302 Found,304 Not Modified,307 Temporary Redirect,308 Permanent Redirect... - 4xx Cliente —
400 Bad Request,401 Unauthorized,403 Forbidden,404 Not Found,409 Conflict,422 Unprocessable Entity,429 Too Many Requests... - 5xx Servidor —
500 Internal Server Error,502 Bad Gateway,503 Service Unavailable,504 Gateway Timeout...
Cada entrada incluye una descripción concisa y la referencia RFC.
Cuándo la usarías
- Tu API devuelve
409y quieres saber si "Conflict" es la respuesta correcta para tu caso. - Estás escribiendo documentación y necesitas elegir entre
401y403. - Te encuentras un
418 I'm a teapoty quieres confirmar que sí, existe en RFC 2324. - Buscas una redirección que mantenga el método
POST(307o308, no301/302).
Cómo funciona
Los datos están embebidos en la página — no hay petición de red. La búsqueda hace coincidencia parcial sobre código, nombre y descripción.
Las referencias RFC son enlaces directos a la spec correspondiente (RFC 7231, 9110, 6585, etc.).
Notas
¿Y los códigos no estándar? Incluimos los más comunes (520-599 de Cloudflare, 598 Network read timeout de algunos proxies) marcados como tales. Los códigos verdaderamente propietarios o sin documentar no.
401 vs 403 — ¿la regla rápida? 401: "no sé quién eres" (sin auth o auth inválida). 403: "sé quién eres pero no puedes". Si no estás seguro, mira la sección 6.5.3 de RFC 9110.
422 vs 400 — ¿la regla rápida? 400: la petición es sintácticamente errónea (JSON inválido, falta un header). 422: sintácticamente correcta pero semánticamente inaceptable (campos válidos pero combinación imposible).
Herramientas relacionadas
- cURL ↔ fetch — para reproducir una petición que devuelve un código inesperado
- Decodificador JWT — un
401conWWW-Authenticate: Bearersuele significar token expirado