A searchable reference for standard HTTP status codes. Quickly find definitions, common causes, and specification details.
The initial part of a request has been received and has not yet been rejected by the server. The server intends to send a final response after the request has been fully received and acted upon.
RFC 7231, Section 6.2.1
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.
RFC 7231, Section 6.2.2
An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.
RFC 2518, Section 10.1
Used to return some response headers before final HTTP message.
RFC 8297
The request has succeeded. The information returned with the response is dependent on the method used in the request.
RFC 7231, Section 6.3.1
The request has been fulfilled and has resulted in one or more new resources being created.
RFC 7231, Section 6.3.2
The request has been accepted for processing, but the processing has not been completed.
RFC 7231, Section 6.3.3
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.
RFC 7231, Section 6.3.4
The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.
RFC 7231, Section 6.3.5
The server successfully fulfilled the request and desires that the user agent reset the "document view", which caused the request to be sent, to its original state.
RFC 7231, Section 6.3.6
The server is successfully fulfilling a range request for the target resource.
RFC 7233, Section 4.1
The target resource has more than one representation, each with its own more specific identifier.
RFC 7231, Section 6.4.1
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.
RFC 7231, Section 6.4.2
The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the effective request URI for future requests.
RFC 7231, Section 6.4.3
The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.
RFC 7231, Section 6.4.4
A conditional GET or HEAD request has been received and would have resulted in a 200 (OK) response if it were not for the fact that the condition evaluated to false.
RFC 7232, Section 4.1
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.
RFC 7231, Section 6.4.7
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 HTTP method MUST NOT change.
RFC 7538
The server cannot or will not process the request due to something that is perceived to be a client error.
RFC 7231, Section 6.5.1
The request has not been applied because it lacks valid authentication credentials for the target resource.
RFC 7235, Section 3.1
Reserved for future use.
RFC 7231, Section 6.5.2
The server understood the request but refuses to authorize it.
RFC 7231, Section 6.5.3
The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
RFC 7231, Section 6.5.4
The method received in the request-line is known by the origin server but not supported by the target resource.
RFC 7231, Section 6.5.5
The target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields.
RFC 7231, Section 6.5.6
The server did not receive a complete request message within the time that it was prepared to wait.
RFC 7231, Section 6.5.7
The request could not be completed due to a conflict with the current state of the target resource.
RFC 7231, Section 6.5.8
The server is refusing to process a request because the request payload is larger than the server is willing or able to process.
RFC 7231, Section 6.5.11
The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.
RFC 7231, Section 6.5.13
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot".
RFC 2324
The server understands the content type of the request entity, and the syntax of the request entity is correct, but was unable to process the contained instructions.
RFC 4918, Section 11.2
The user has sent too many requests in a given amount of time ("rate limiting").
RFC 6585, Section 4
The server encountered an unexpected condition that prevented it from fulfilling the request.
RFC 7231, Section 6.6.1
The server does not support the functionality required to fulfill the request.
RFC 7231, Section 6.6.2
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.
RFC 7231, Section 6.6.3
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.
RFC 7231, Section 6.6.4
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.
RFC 7231, Section 6.6.5