Complete reference for all HTTP status codes with search and filtering
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client via Upgrade header.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message.
The request has succeeded.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The returned meta-information is from a local or third-party copy, not the origin server.
The server has fulfilled the request but does not need to return an entity-body.
The server has fulfilled the request and the user agent should reset the document view.
The server has fulfilled the partial GET request for the resource.
Conveys information about multiple resources in situations where multiple status codes might be appropriate.
Members of a DAV binding have already been enumerated in a previous reply.
The server has fulfilled a GET request for the resource with instance manipulations applied.
The target resource has more than one representation, each with its own URI.
The target resource has been assigned a new permanent URI.
The target resource resides temporarily under a different URI.
The server is redirecting the user agent to a different resource via GET.
The resource has not been modified since the last request.
The requested resource must be accessed through the proxy given by the Location field.
The target resource resides temporarily under a different URI; method and body must not change.
The target resource has been assigned a new permanent URI; method and body must not change.
The server cannot process the request due to client error (malformed request syntax, invalid framing, etc.).
The request requires user authentication.
Reserved for future use — intended for digital payment systems.
The server understood the request but refuses to authorize it.
The origin server did not find a current representation for the target resource.
The method received in the request-line is not supported by the target resource.
The target resource does not have a representation acceptable per Accept headers.
The client must first authenticate itself with the proxy.
The server did not receive a complete request message within the time it was prepared to wait.
The request could not be completed due to a conflict with the current state of the target resource.
The target resource is no longer available and no forwarding address is known.
The server refuses to accept the request without a defined Content-Length.
One or more conditions given in the request header fields evaluated to false.
The request payload is larger than the server is willing to process.
The request-target is longer than the server is willing to interpret.
The origin server refuses the request because the payload is in an unsupported format.
None of the ranges in the Range header field overlap the current extent of the selected resource.
The expectation given in the Expect header field could not be met by the server.
The server refuses to brew coffee because it is, permanently, a teapot.
The request was directed at a server that is not able to produce a response.
The server understands the content type and syntax but was unable to process the contained instructions.
The source or destination resource of a method is locked.
The method could not be performed because the requested action depended on another action that failed.
The server is unwilling to risk processing a request that might be replayed.
The server refuses to perform the request using the current protocol.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time.
The server is unwilling to process the request because its header fields are too large.
The server is denying access to the resource as a consequence of a legal demand.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server, while acting as a gateway or proxy, received an invalid response from an inbound server.
The server is currently unable to handle the request due to temporary overloading or maintenance.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
The server does not support the major version of HTTP that was used in the request.
Transparent content negotiation for the request results in a circular reference.
The method could not be performed on the resource because the server is unable to store the representation.
The server detected an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access.