HTTP 状态码参考
HTTP 状态码完整参考。按代码、名称或描述搜索。
1xx Informational
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.
2xx Success
OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server.
No Content
The server successfully processed the request but is not returning any content.
Reset Content
The server successfully processed the request and asks the client to reset the 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 statuses (WebDAV).
Already Reported
Members of a DAV binding have already been enumerated (WebDAV).
IM Used
The server has fulfilled a GET request and the response represents instance-manipulations.
3xx Redirection
Multiple Choices
The request has more than one possible response. The user should choose one of them.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Found
The URI of the requested resource has been changed temporarily.
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Use Proxy
The requested resource is only available through a proxy (deprecated).
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
Permanent Redirect
The resource is now permanently located at another URI, specified by the Location header.
4xx Client Error
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 been provided.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The requested resource could not be found on the server.
Method Not Allowed
The request method is not supported for the requested resource.
Not Acceptable
The requested resource is only capable of generating content not acceptable according to the 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 requested resource.
Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
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 or resource does not support.
Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot (April Fools' joke, RFC 2324).
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors (WebDAV).
Locked
The resource that is being accessed is locked (WebDAV).
Failed Dependency
The request failed because it depended on another request and that request failed (WebDAV).
Too Early
The server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The client should switch to a different protocol.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Unavailable For Legal Reasons
A server operator has received a legal demand to deny access to a resource.
5xx Server Error
Internal Server Error
A generic error message when the server encounters an unexpected condition.
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway or proxy 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.
Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
Insufficient Storage
The server is unable to store the representation needed to complete the request (WebDAV).
Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
HTTP Status Codes - 技术详情
HTTP status codes are standardized responses from web servers. They are grouped into 5 classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
命令行替代方案
# Check HTTP status with curl\ncurl -I -s https://example.com | head -n 1\n\n# Get full response headers\ncurl -I https://example.com