Filuni

HTTP 状态码

完整 HTTP 状态码速查表,可按编号搜索。

1xx Informational

100
Continue
The initial part of a request was received, please continue.
101
Switching Protocols
The server is switching protocols as requested by the client.

2xx Success

200
OK
The request has succeeded.
201
Created
The request has been fulfilled and a new resource was created.
202
Accepted
The request has been accepted for processing.
204
No Content
The request was successful but there is no content to return.
206
Partial Content
Partial content delivered as requested by a Range header.

3xx Redirection

301
Moved Permanently
The resource has been moved to a new URL permanently.
302
Found
The resource is temporarily located at a different URL.
304
Not Modified
Cached version is still valid; no body returned.
307
Temporary Redirect
Same as 302 but the method must not change.
308
Permanent Redirect
Same as 301 but the method must not change.

4xx Client Error

400
Bad Request
The server cannot process the request due to a client error.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found.
405
Method Not Allowed
The request method is not supported for this resource.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is no longer available and will not be available again.
413
Payload Too Large
The request body is larger than the server is willing to process.
415
Unsupported Media Type
The media type is not supported by the server.
422
Unprocessable Entity
The request was well-formed but contained semantic errors.
429
Too Many Requests
The user has sent too many requests in a given time (rate limited).

5xx Server Error

500
Internal Server Error
A generic server error.
501
Not Implemented
The server does not support the functionality required.
502
Bad Gateway
Invalid response from an upstream server.
503
Service Unavailable
The server is overloaded or down for maintenance.
504
Gateway Timeout
Upstream server failed to respond in time.
隐私安全全部在浏览器本地完成，数据不上传
简单易用粘贴或输入即可，结果实时呈现
永久免费不限次数，无需注册
快速高效先进技术，处理高效稳定

当一个 API 或页面只回了一个数字，比如 404 或 502，其实它已经准确告诉了你哪里出了问题，前提是你认得这个码。本工具是一份完整、可搜索的 HTTP 状态码参考，按类别分组，让你查一个码就能判断问题出在你的请求、服务器，还是只是一次重定向。

4044xx
状态码 → 含义

使用步骤: HTTP 状态码

  1. 1输入内容在搜索框输入状态码数字或关键词(如 404、未找到)。
  2. 2设置选项从匹配列表中找到对应的 HTTP 状态码。
  3. 3开始处理阅读它的分类(1xx-5xx)与含义说明。
  4. 4获取结果复制状态码或描述,用于文档或接口排错。

常见用途

排查 API 调用查一下请求返回的状态码，看是该修请求还是修服务器。
选对要返回的状态为自己的接口选择正确的状态码，而不是一律返回 200 或 500。
读懂服务器日志一眼看明白访问日志里那一串状态数字的含义。
分清 401 与 403当两个相近的码容易混淆时，核对它们的确切含义。

使用提示

首位数字代表类别1xx 是信息，2xx 成功，3xx 重定向，4xx 是你的请求，5xx 是服务器。单看首位就知道该往哪边查。
401 不是 403401 表示你尚未通过身份验证，403 表示你已通过验证但没有权限，两者需要不同的处理。
有些码很少见或非官方你偶尔会遇到像 418 这样的玩笑码或厂商自定义码，不要围绕这些冷僻的码去写逻辑。
状态码是线索，不是全部数字能把范围缩小，但真正的错误细节往往在响应正文里，两者要一起看。

常见问题