Consulta rápida para códigos HTTP 1xx-5xx, semântica RFC 9110, cacheabilidade e regras de retry.
Rate limit exceeded. Respect Retry-After header with exponential backoff + jitter.
{ "status": 429, "error": "Too Many Requests", "message": "Rate limit exceeded. Respect Retry-After header with exponential backoff + jitter.", "retryable": true, "spec": "RFC 6585" }
Initial request headers received; client may proceed sending request body.
Server agrees to upgrade connection protocol (e.g., HTTP/1.1 -> WebSocket).
Sends Link preload headers before final response is ready.
Request succeeded cleanly and response body holds requested representation.
Request succeeded and created one or more new resources (often paired with Location header).
Request accepted for async background processing; outcome is pending.
Succeeded with intentionally empty response body (common for DELETE/PUT/OPTIONS).
Delivering requested byte range for resumable downloads or media streaming.
Target resource permanently relocated to Location URI (SEO link equity passes).
Temporary redirect; browsers may rewrite POST to GET unless 307 is used.
Cached representation still matches ETag or If-Modified-Since; no body sent.
Temporary redirect that strictly preserves original HTTP method and body.
Permanent redirect that strictly preserves HTTP method (preferred over 301 for APIs).
Malformed syntax, invalid JSON, missing fields, or failed schema validation.
Missing or invalid authentication credentials (JWT/API key expired or absent).
Identity is known, but lacks permission/scope/ACL or blocked by WAF.
Origin could not find requested route or entity ID.
Endpoint exists, but HTTP verb (GET/POST/DELETE) is unsupported; check Allow header.
Server closed idle connection before client finished sending complete request.
Request conflicts with current resource state (duplicate key, version/ETag mismatch).
Resource permanently deleted and will not return (de-indexes faster than 404).
Payload exceeds server or proxy limit (check Nginx client_max_body_size).
Request Content-Type header (e.g., text/plain vs application/json) rejected.
April Fools HTCPCP status code reserved permanently in RFC 9110.
Syntax is valid JSON/XML, but domain/semantic validation rules failed.
Blocked due to government censorship, DMCA, or court order.
Unhandled exception or crash on the origin application server.
Reverse proxy/gateway received invalid, empty, or refused response from upstream.
Server temporarily overloaded or in maintenance mode; check Retry-After header.
Reverse proxy waited too long for upstream application to respond.
Cloudflare-specific: origin returned empty/unexpected response or closed TCP.
Cloudflare-specific: TCP handshake to origin server timed out (firewall/overload).
Cloudflare-specific: origin connected, but took >100s without sending HTTP response.
Fixe esta ferramenta no painel lateral do seu navegador
Acesse este utilitário a qualquer momento com Alt+M sem trocar de aba. 100% offline e gratuito.
Este catálogo RFC 9110 e edge roda inteiramente na memória do navegador para resposta rápida a incidentes.
MiniToolDesk é 100% gratuito e local. Seu apoio mantém o projeto sem anúncios.
Formate, indente e embeleze consultas SQL para MySQL, PostgreSQL e SQLite em memória
Decodifique e inspecione JSON Web Tokens (JWT) com total segurança na memória local
Conversão bidirecional entre YAML e JSON com validação sintática em tempo real
Conversão de armazenamento (KB/KiB, MB/MiB, GB/GiB), CSS (px para rem), comprimento e velocidade