An informational response indicates that the request was received and understood.
The initial part of a request has been received and has not yet been rejected by the server.
The server understands and is willing to comply with the client's request, via the Upgrade header field, for a change in the application protocol being used on this connection.
An interim response used to inform the client that the server has accepted the full request, but has not yet completed it.
This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.
The client's request was successfully received, understood, and accepted.
The request was successful.
The request was successful and has resulted in one or more new resources being created.
The request has been accepted for processing, but the processing has not been completed.
The request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy.
The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.
The server has fulfilled the request and desires that the user agent resets the "document view", which caused the request to be sent, to its original state as received from the origin server.
The server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation, that correspond to the satisfiable ranges found in the requests's Range header field.
Provides status for multiple independent operations.
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
Indicates that further action needs to be taken by the user agent in order to fulfill the request.
The target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to one or more of those identifiers.
The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.
The target resource resides temporarily under a different URI.
The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, that is intended to provide an indirect response to the original request.
A conditional GET request has been received and would have resulted in a 200 (OK) response if it were not for the fact that the condition has evaluated to false.
The target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.
The target resource has been assigned a new permanent URI and any future references to this resource outght to use one of the enclosed URIs. This status code is similar to 301 Moved Permanently, except that it does not allow rewriting the request method from POST to GET.
The client seems to have erred. It most likely means that the client is sending a faulty request in some way.
The server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process.
The client must authenticate itself with valid credentials to get the requested response.
A nonstandard client error status response code that is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
The server understood the request but refuses to authorize it. Unlike 401, the client's identity is known to the server.
A classic! The server can not find the requested resource. The URL is not recognized - or - the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client.
Method Not Allowed
The request method is known by the server but has been disabled for this endpoint and cannot be used. For example, the client sent a GET request instead of a POST.
The target resource does not have a current representation that would be acceptable to the user agent, and the server is unwilling to supply a default representation, after performing "server-driven content negotiation".
Proxy Authentication Required
Similar to 401 (Unauthorized), but indicates that the client needs to authenticate itself in order to use a proxy.
The server did not receive a complete request message within the time that it was prepared to wait.
The request could not be completed due to a conflict with the current state of the resource.
Access to the target resource is no longer available at the origin server and that this condition is likely to be permanent.
The server refuses to accept the request without a defined Content-Length.
One or more preconditions given in the request header fields evaluated to false when tested on the server.
Payload Too Large
The server is refusing to process a request because the request payload is larger than the server is willing or able to process.
URI Too Long
The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
Unsupported Media Type
The origin server is refusing to service the request because the payload is in a format not supported by the target resource for this method.
Range Not Satisfiable
None of the ranges in the request's Range header field overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid ranges or an excessive request of small or overlapping ranges.
The expectation given in the request's Expect header field could not be met by at least one of the inbound servers.
I'm a teapot
Any attempt to brew coffee with a teapot should result in the error code 418 I'm a teapot.
The server understands the content type of the request entity (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions.
The source or destination resource of a method is locked.
The method could not be performed on the resource because the requested action depended on another action and that action failed.
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.
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
The server is denying access to the resource in response to a legal demand.
The server is aware that it has erred or is incapable of performing the requested method.
Internal Server Error
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 it accessed while attempting to fulfill the request.
The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.
HTTP Version Not Supported
The server does not support, or refuses to support, the protocol version that was used in the request message.
Variant Also Negotiates
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
Network Authentication Required
The client needs to authenticate to gain network access.