HTTP Status Code Reference
Search common HTTP response status codes and their meanings. Search rows quickly with a compact table UI.
- Use a small sample first, then process the full non-sensitive input.
- Review the output before copying it into documentation, code, or another system.
- Keep the original text nearby so changed formatting, encoding, units, or whitespace can be compared.
| Code | Reason phrase | Class | Meaning / common use |
|---|---|---|---|
| 100 | Continue | 1xx Informational | Client can continue sending the request |
| 101 | Switching Protocols | 1xx Informational | Protocol switch accepted |
| 103 | Early Hints | 1xx Informational | Preload links before final response |
| 200 | OK | 2xx Success | Request succeeded |
| 201 | Created | 2xx Success | Resource created |
| 202 | Accepted | 2xx Success | Accepted for processing |
| 204 | No Content | 2xx Success | Success with no response body |
| 206 | Partial Content | 2xx Success | Range request response |
How to use this reference
Search by keyword, protocol, code, permission, extension, or command. Copy a single row or the filtered result set for notes, tickets, configuration checks, or documentation drafts.
HTTP Status Code Reference 的具体使用判断
HTTP Status Code Reference 适合处理明确、短小、非敏感的 参考查询 任务。页面保留为独立入口，是为了让用户在知道具体任务名称时能直接打开，而不是在一个大型混合工具里反复切换。Search common HTTP response status codes and their meanings. Search rows quickly with a compact table UI. 这样的任务通常耗时不长，但错误复制到目标系统后会造成排查成本，因此需要在复制前完成最基本的上下文检查。
重点确认参考值来源、适用环境和版本差异。参考表适合快速定位，不替代官方规范或业务系统。 对于 pagecode 这类页面，建议使用公开样例学习操作，再处理自己的脱敏输入。输出结果如果会进入代码、配置、文档、表格、邮件、工单或客户交付材料，应把原始输入和工具输出并排保存，至少确认一次目标系统如何解释该结果。
不建议使用本页的情况
- 输入包含密码、密钥、token、客户资料、内部域名或完整生产日志。
- 任务需要权限、审计记录、团队审批、官方控制台或专用 SDK。
- 你需要的是安全证明、合规结论、工程设计结论或财务最终数值。