1xx〜5xx HTTP および Cloudflare ステータスコード、キャッシュ可否、リトライ判定を即座に確認。
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.
ブラウザのサイドパネルにこのツールを固定
タブを切り替えずに Alt+M でいつでも即座に呼び出し可能。完全オフライン・無料。
全 RFC データがブラウザ内で動作するため、障害対応中も即座に仕様を確認できます。
MiniToolDesk は 100% 無料かつクライアントサイド動作です。皆様の応援が支えです。
MySQL、PostgreSQL、SQLiteのSQLクエリをブラウザ内で安全に整形・インデント
JSON Web Token (JWT) のヘッダー、ペイロード、有効期限をローカルで安全に解析
YAMLとJSONをリアルタイムに双方向変換・構文検証・インデント調整
データ容量 (KB/KiB, MB/MiB, GB/GiB)、CSS (px/rem)、長さ、速度、温度を高精度変換