HTTP 狀態碼
HTTP 狀態碼 可直接在瀏覽器中使用，讓你不用安裝額外軟體就能快速完成常見任務。
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
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.
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 meta-information is from a local or third-party copy.
No Content
The server successfully processed the request but is not returning any content.
Reset Content
The server successfully processed the request and is not returning any content, 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 status codes for multiple independent operations.
Already Reported
The members of a DAV binding have already been enumerated.
IM Used
The server has fulfilled a GET request and the response is a representation of one or more instance-manipulations.
Multiple Choices
There are multiple options for the resource that the client may follow.
Moved Permanently
The resource has been permanently moved to a new URL.
Found
The resource resides temporarily under a different URL.
See Other
The response can be found under a different URL using a GET method.
Not Modified
The resource has not been modified since the last request.
Use Proxy
The requested resource must be accessed through the proxy.
Temporary Redirect
The request should be repeated with another URL, but future requests should still use the original URL.
Permanent Redirect
The request and all future requests should be repeated using another URL.
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use. Originally intended for digital payment schemes.
Forbidden
The client does not have access rights to the content.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is not supported for the requested resource.
Not Acceptable
The server cannot produce a response matching the list of acceptable values.
Proxy Authentication Required
Authentication with the proxy is required.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the server.
Gone
The requested content has been permanently deleted from the server.
Length Required
The server requires the Content-Length header field.
Precondition Failed
The server does not meet one of the preconditions set by the client.
Payload Too Large
The request entity is larger than limits defined by the server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported.
Range Not Satisfiable
The range specified in the Range header cannot be fulfilled.
Expectation Failed
The expectation given in the Expect header could not be met.
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot.
Unprocessable Entity
The request was well-formed but unable to be followed due to semantic errors.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed because it depended on another request that failed.
Too Early
The server is unwilling to process 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.
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Unavailable For Legal Reasons
The resource is unavailable due to legal demands.
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server.
Bad Gateway
The server received an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request, often due to maintenance or overload.
Gateway Timeout
The server is acting as a gateway and did not get a response in time.
HTTP Version Not Supported
The HTTP version used in the request is not supported.
Variant Also Negotiates
The server has an internal configuration error.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
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.