HTTP 状态码
所有 HTTP 状态码参考指南，包含说明和用例。
HTTP Status Codes
Browse and search all standard HTTP status codes with descriptions.
| Code | Name | Description |
|---|---|---|
| 100 | Continue | The server has received the request headers and the client should proceed to send the request body. |
| 101 | Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. |
| 102 | Processing | The server has received and is processing the request, but no response is available yet. |
| 103 | Early Hints | Used to return some response headers before final HTTP message. |
| 200 | OK | The request has succeeded. The meaning of the success depends on the HTTP method. |
| 201 | Created | The request has been fulfilled and resulted in a new resource being created. |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. |
| 203 | Non-Authoritative Information | The returned metadata is not exactly the same as is available from the origin server. |
| 204 | No Content | The server successfully processed the request and is not returning any content. |
| 205 | Reset Content | The server successfully processed the request, asks that the requester reset its document view. |
| 206 | Partial Content | The server is delivering only part of the resource due to a range header sent by the client. |
| 207 | Multi-Status | The message body contains an XML message and can contain multiple response codes. |
| 208 | Already Reported | The members of a DAV binding have already been enumerated in a preceding part of the response. |
| 226 | IM Used | The server has fulfilled a request for the resource and the response is a representation of the result. |
| 300 | Multiple Choices | Indicates multiple options for the resource from which the client may choose. |
| 301 | Moved Permanently | This and all future requests should be directed to the given URI. |
| 302 | Found | Tells the client to look at another URL. The original URL should still be used in future requests. |
| 303 | See Other | The response to the request can be found under another URI using the GET method. |
| 304 | Not Modified | Indicates that the resource has not been modified since the version specified by the request headers. |
| 307 | Temporary Redirect | The request should be repeated with another URI but future requests should still use the original URI. |
| 308 | Permanent Redirect | This and all future requests should be directed to the given URI. The method must not change. |
| 400 | Bad Request | The server cannot or will not process the request due to an apparent client error. |
| 401 | Unauthorized | Authentication is required and has failed or has not been provided. |
| 402 | Payment Required | Reserved for future use. Occasionally used to indicate a quota has been exceeded. |
| 403 | Forbidden | The server understood the request but refuses to authorize it. |
| 404 | Not Found | The requested resource could not be found but may be available in the future. |
| 405 | Method Not Allowed | A request method is not supported for the requested resource. |
| 406 | Not Acceptable | The requested resource is capable of generating only content not acceptable according to the Accept headers. |
| 407 | Proxy Authentication Required | The client must first authenticate itself with the proxy. |
| 408 | Request Timeout | The server timed out waiting for the request. |
| 409 | Conflict | Indicates that the request could not be processed because of conflict in the current state of the resource. |
| 410 | Gone | The resource requested is no longer available and will not be available again. |
| 411 | Length Required | The request did not specify the length of its content, which is required by the requested resource. |
| 412 | Precondition Failed | The server does not meet one of the preconditions that the requester put on the request. |
| 413 | Payload Too Large | The request is larger than the server is willing or able to process. |
| 414 | URI Too Long | The URI provided was too long for the server to process. |
| 415 | Unsupported Media Type | The request entity has a media type which the server or resource does not support. |
| 416 | Range Not Satisfiable | The client has asked for a portion of the file, but the server cannot supply that portion. |
| 417 | Expectation Failed | The server cannot meet the requirements of the Expect request-header field. |
| 418 | I'm a Teapot | The server refuses the attempt to brew coffee with a teapot. (RFC 2324, April Fools joke) |
| 421 | Misdirected Request | The request was directed at a server that is not able to produce a response. |
| 422 | Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors. |
| 423 | Locked | The resource that is being accessed is locked. |
| 424 | Failed Dependency | The request failed because it depended on another request and that request failed. |
| 425 | Too Early | Indicates that the server is unwilling to risk processing a request that might be replayed. |
| 426 | Upgrade Required | The client should switch to a different protocol such as TLS/1.3. |
| 428 | Precondition Required | The origin server requires the request to be conditional. |
| 429 | Too Many Requests | The user has sent too many requests in a given amount of time (rate limiting). |
| 431 | Request Header Fields Too Large | The server is unwilling to process the request because its header fields are too large. |
| 451 | Unavailable For Legal Reasons | The user requested a resource that cannot legally be provided. |
| 500 | Internal Server Error | A generic error message, given when an unexpected condition was encountered. |
| 501 | Not Implemented | The server either does not recognize the request method, or lacks the ability to fulfill the request. |
| 502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
| 503 | Service Unavailable | The server is currently unavailable (overloaded or down for maintenance). |
| 504 | Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. |
| 505 | HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request. |
| 506 | Variant Also Negotiates | Transparent content negotiation for the request results in a circular reference. |
| 507 | Insufficient Storage | The server is unable to store the representation needed to complete the request. |
| 508 | Loop Detected | The server detected an infinite loop while processing the request. |
| 510 | Not Extended | Further extensions to the request are required for the server to fulfill it. |
| 511 | Network Authentication Required | The client needs to authenticate to gain network access. |
How to Use
- 使用HTTP Status Codes浏览或查询信息。
- 按关键词搜索或按分类浏览。
- 复制相关信息用于项目。
Frequently Asked Questions
- 是完整参考吗？
- HTTP Status Codes 涵盖最常用条目，边缘情况请查阅官方规范。
- 多久更新一次？
- 基于稳定标准，重大更新会反映。
- 能离线使用吗？
- 加载后可离线使用，收藏页面方便快速访问。