带描述的完整HTTP状态码参考。
HTTP状态码是Web服务器返回的标准化响应代码。它们指示特定HTTP请求是否已成功完成。理解这些代码对于Web开发、API集成和调试至关重要。最常见的代码包括200（OK）、301（永久移动）、404（未找到）和500（内部服务器错误）。
50 个状态码
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before final HTTP message.
OK
The request has succeeded. The meaning of the success depends on the HTTP method.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The server is a transforming proxy that received a 200 OK from its origin.
No Content
The server successfully processed the request and is not returning any content.
Reset Content
The server successfully processed the request, asks the requester to reset its document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multi-Status
The message body contains multiple separate response codes.
Already Reported
The members of a DAV binding have already been enumerated in a previous reply.
IM Used
The server has fulfilled a request for the resource, and the response represents instance-manipulations.
Multiple Choices
Indicates multiple options for the resource from which the client may choose.
Moved Permanently
This and all future requests should be directed to the given URI.
Found
Tells the client to look at another URL. Previously "Moved Temporarily".
See Other
The response to the request can be found under another URI using the GET method.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Temporary Redirect
The request should be repeated with another URI; however, future requests should still use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
Authentication is required and has failed or has not yet been provided.
Payment Required
Reserved for future use. The original intention was for digital payment schemes.
Forbidden
The request was valid, but the server is refusing action. The user might not have permissions.
Not Found
The requested resource could not be found but may be available in the future.
Method Not Allowed
A request method is not supported for the requested resource.
Not Acceptable
The requested resource is capable of generating only content not acceptable per Accept headers.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
The request could not be processed because of conflict in the current state of the resource.
Gone
The resource requested is no longer available and will not be available again.
Length Required
The request did not specify the length of its content, which is required by the resource.
Precondition Failed
The server does not meet one of the preconditions that the requester put on the request header.
Payload Too Large
The request is larger than the server is willing or able to process.
URI Too Long
The URI provided was too long for the server to process.
Unsupported Media Type
The request entity has a media type which the server does not support.
Range Not Satisfiable
The client has asked for a portion of the file that the server cannot supply.
I'm a Teapot
The server refuses the attempt to brew coffee with a teapot. (April Fools RFC 2324)
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Unavailable For Legal Reasons
A server operator has received a legal demand to deny access to a resource.
Internal Server Error
A generic error message when an unexpected condition was encountered.
Not Implemented
The server does not recognize the request method, or it lacks the ability to fulfill the request.
Bad Gateway
The server was acting as a gateway and received an invalid response from the upstream server.
Service Unavailable
The server cannot handle the request (overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway and did not receive a timely response from the upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Network Authentication Required
The client needs to authenticate to gain network access.