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
WebDAV. The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before the final HTTP message, allowing the client to start preloading resources.
OK
The request succeeded. The result meaning depends on the HTTP method used.
Created
The request succeeded and a new resource was created as a result. Typically the response to POST or PUT.
Accepted
The request has been received but not yet acted upon. It is non-committal and intended for asynchronous processing.
Non-Authoritative Information
The returned metadata is from a local or third-party copy rather than the origin server.
No Content
The server successfully processed the request and is not returning any content in the body.
Reset Content
Tells the client to reset the document view, for example to clear a form after submission.
Partial Content
The server is delivering only part of the resource due to a Range header sent by the client.
Multi-Status
WebDAV. Conveys information about multiple resources where several status codes might be appropriate.
Already Reported
WebDAV. The members of a binding have already been enumerated in a preceding part of the response.
IM Used
The server has fulfilled a GET request and the response represents the result of instance manipulations applied to the current instance.
Multiple Choices
The request has more than one possible response. The user or user agent 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 requested resource resides temporarily under a different URL. The client should keep using the original URL.
See Other
Directs the client to get the requested resource at another URL with a GET request.
Not Modified
Used for caching. The response has not been modified, so the client can continue to use the cached version.
Use Proxy
Deprecated. Indicates that the requested response must be accessed through a proxy.
Temporary Redirect
The resource resides temporarily at a different URL and the request method must not be changed when reissuing.
Permanent Redirect
The resource now permanently lives at a different URL and the request method must not be changed.
Bad Request
The server cannot process the request due to a client error such as malformed syntax or invalid framing.
Unauthorized
Authentication is required and has failed or not been provided. Semantically means 'unauthenticated'.
Payment Required
Reserved for future use. Sometimes used by APIs to signal that payment or a paid plan is required.
Forbidden
The client is authenticated but does not have permission to access the requested resource.
Not Found
The server cannot find the requested resource. The URL is not recognized.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the list of acceptable values in the request's Accept headers.
Proxy Authentication Required
Similar to 401, but authentication is needed for a proxy.
Request Timeout
The server timed out waiting for the request. The client may repeat the request without modifications.
Conflict
The request conflicts with the current state of the server, such as an edit conflict.
Gone
The requested content has been permanently deleted from the server with no forwarding address.
Length Required
The server rejected the request because the Content-Length header field is not defined and is required.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
The request entity is larger than limits defined by the server. The server may close the connection.
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 by the server, so it rejects the request.
Range Not Satisfiable
The range specified by the Range header field in the request cannot be fulfilled.
Expectation Failed
The expectation indicated by the Expect request header field cannot be met by the server.
I'm a teapot
The server refuses to brew coffee because it is, permanently, a teapot. An April Fools' joke from RFC 2324.
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Content
The request was well-formed but could not be followed due to semantic errors. Common in validation.
Locked
WebDAV. The resource that is being accessed is locked.
Failed Dependency
WebDAV. The request failed because it depended on another request that failed.
Too Early
Indicates the server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current protocol but might after the client upgrades.
Precondition Required
The origin server requires the request to be conditional to prevent lost updates.
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
The requested resource is unavailable due to legal demands, such as government censorship.
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The request method is not supported by the server and cannot be handled. Only GET and HEAD are required.
Bad Gateway
The server, while acting as a gateway or proxy, 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, acting as a gateway, did not get a response in time from the upstream server.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error in transparent content negotiation.
Insufficient Storage
WebDAV. The server is unable to store the representation needed to complete the request.
Loop Detected
WebDAV. 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, often used by captive portals.
100% Private
This reference runs entirely in your browser. Nothing uploaded.