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。