HTTP 狀態代碼查詢
查詢任何 HTTP 狀態代碼——1xx 到 5xx——帶純英文描述。
- 100Continue
Server received the request headers; client should send the body.
- 101Switching Protocols
The server is switching protocols as requested by the client.
- 102Processing
Request received but not yet processed (WebDAV).
- 103Early Hints
Used to return some response headers before final HTTP message.
- 200OK
Standard success response.
- 201Created
Request succeeded and a new resource was created.
- 202Accepted
Request accepted for processing but not completed.
- 203Non-Authoritative Information
Returned metadata is from a third-party copy.
- 204No Content
Request succeeded but no content is returned.
- 205Reset Content
Request succeeded; client should reset the document view.
- 206Partial Content
Range request succeeded; partial content returned.
- 207Multi-Status
Body contains multiple statuses (WebDAV).
- 208Already Reported
Members of a DAV binding already enumerated.
- 226IM Used
Server fulfilled a GET request and the response is the result of one or more instance-manipulations.
- 300Multiple Choices
Request has more than one possible response.
- 301Moved Permanently
Resource moved to a new permanent URL.
- 302Found
Resource is temporarily at a different URL.
- 303See Other
Client should follow the response to a new URL with GET.
- 304Not Modified
Cached version is still valid; no body returned.
- 307Temporary Redirect
Same method should be used at the new URL.
- 308Permanent Redirect
Same as 301 but the request method must not change.
- 400Bad Request
Server cannot or will not process due to a client error.
- 401Unauthorized
Authentication required and has failed or not been provided.
- 402Payment Required
Reserved for future use, sometimes used for paywalls.
- 403Forbidden
Server understood but refuses to authorize.
- 404Not Found
The requested resource could not be found.
- 405Method Not Allowed
Request method is known but not supported by the resource.
- 406Not Acceptable
Resource cannot produce content matching the Accept headers.
- 407Proxy Authentication Required
Client must authenticate with the proxy.
- 408Request Timeout
Server timed out waiting for the request.
- 409Conflict
Request conflicts with the current state of the resource.
- 410Gone
Resource is no longer available and will not be available again.
- 411Length Required
Content-Length header is required.
- 412Precondition Failed
A precondition in the request headers was not met.
- 413Payload Too Large
Request entity is larger than the server is willing to process.
- 414URI Too Long
URI is longer than the server is willing to interpret.
- 415Unsupported Media Type
Media format of the request is not supported.
- 416Range Not Satisfiable
Requested range cannot be served.
- 417Expectation Failed
Expectation in Expect header could not be met.
- 418I'm a teapot
Server refuses to brew coffee because it is, permanently, a teapot.
- 421Misdirected Request
Request was directed to a server unable to produce a response.
- 422Unprocessable Entity
Request was well-formed but had semantic errors.
- 423Locked
Resource is locked (WebDAV).
- 424Failed Dependency
Request failed because of a previous failed request (WebDAV).
- 425Too Early
Server unwilling to risk processing a replay-vulnerable request.
- 426Upgrade Required
Client must upgrade to a different protocol.
- 428Precondition Required
Server requires the request to be conditional.
- 429Too Many Requests
Client has sent too many requests in a given amount of time.
- 431Request Header Fields Too Large
Headers are too large for the server to process.
- 451Unavailable For Legal Reasons
Resource cannot be served for legal reasons.
- 500Internal Server Error
Generic server error response.
- 501Not Implemented
Server does not support the request method.
- 502Bad Gateway
Server received an invalid response from an upstream server.
- 503Service Unavailable
Server is overloaded or down for maintenance.
- 504Gateway Timeout
Upstream server did not respond in time.
- 505HTTP Version Not Supported
HTTP version in the request is not supported.
- 506Variant Also Negotiates
Internal configuration error in transparent content negotiation.
- 507Insufficient Storage
Server is unable to store the representation (WebDAV).
- 508Loop Detected
Server detected an infinite loop while processing (WebDAV).
- 510Not Extended
Further extensions to the request are required.
- 511Network Authentication Required
Client needs to authenticate to gain network access.
來自 RFC 9110 和 IANA HTTP 狀態註冊表。
關於HTTP 狀態代碼查詢
Handytool 的 HTTP 狀態代碼查詢是從 100 Continue 到 511 Network Authentication Required 的每個 HTTP 狀態的快速參考。按代碼（404）、名稱（Not Found）或描述片段搜尋；按類（1xx 資訊、2xx 成功、3xx 重定向、4xx 用戶端錯誤、5xx 伺服器錯誤）過濾。源自 RFC 9110 和 IANA HTTP 狀態登錄，包括您在實際 API 回應中會看到的 WebDAV 和其他延伸。
HTTP 狀態代碼查詢功能
- 01
按代碼或含義搜尋
輸入代碼、名稱或描述中的片語——清單即時過濾。當您記得 422 表示 "某個語義" 但無法想起確切名稱時有用。
- 02
類過濾
將清單縮小到單個類——調試用戶端錯誤時為 4xx、追蹤伺服器錯誤時為 5xx、解開重定向鏈時為 3xx。
- 03
純英文解釋
每個條目都有針對開發人員的單句摘要——代碼實際上在實務中意味著什麼，而不僅僅是正式 RFC 措辭。
HTTP 狀態代碼查詢常見問題
- 401 和 403 有什麼區別？
- 401 Unauthorized 意味著要求缺乏有效驗證——登入並重試。403 Forbidden 意味著您已驗證但不允許存取資源——認證資料無法幫助。
- 何時應該傳回 422 vs 400？
- 400 Bad Request 用於格式不正確的語法（損壞的 JSON、缺少必要欄位）。422 Unprocessable Entity 用於語法上有效但業務驗證失敗的要求（電子郵件已存在、年齡必須 ≥ 18）。
- 418 I'm a teapot 是真實的狀態代碼嗎？
- 是的——在 RFC 2324（1998）中定義為 April Fools' 笑話，在 RFC 7168 中重申。HTTP 本身不使用它，但它出現在 IANA 登錄中，少數服務將其作為復活節彩蛋傳回。
- 511 以上的 5xx 代碼之後發生什麼？
- IANA 登錄中 511 以上的代碼未分配。您可能會看到來自特定平臺的自訂 5xx 代碼（Cloudflare 對上游問題使用 520-527），但它們是供應商特定的延伸，不是標準 HTTP。