⚡️ HTTP Statuscodes
A list of all HTTP response status codes
Informational responses (100 - 199)
Successful responses (200 - 299)
Redirection messages (300 - 399)
Client error responses (400 - 499
Server error responses (500 - 599)
The status codes listed below are defined in RFC 9110.
Note: If you receive a response that is not in this list, it is a Non-standard response that may be tailored to the server’s software.
Informational Responses
100 Continue
This intermediate response indicates that the client should continue the request, or ignore the response if the request has already finished.
101 Switching Protocols
This code is sent in response to an Upgrade Request header from the client and indicates which protocol the server is switching to.
102 Processing (WebDAV)
This code indicates that the server has received and is processing the request, but there is no response yet.
103 Early Hints
This status code is primarily intended for use with the Link header to allow the User-Agent to begin preloading resources while the server prepares a response or preconnects to an origin from which the page needs resources.
Successful Responses
200 OK
The request was successful. The result meaning of “success” depends on the HTTP method:
GET: The resource was retrieved and transmitted in the message body.
HEAD: The representation headers are included in the response without any message body being transmitted.
PUT or POST: The resource describing the result of the action is transmitted in the message body.
TRACE: The message body contains the request message as received from the server.
201 Created The request was successful, and a new resource was created as a result. This is typically the response sent after POST requests or some PUT requests.
202 Accepted
The request has been received but not yet processed. It is non-binding because there is no way in HTTP to later send an asynchronous response indicating the result of the request. It is intended for cases where another process or server is handling the request, or for batch processing.
203 Non-Authoritative Information
This response code means that the metadata returned does not exactly match what is available on the origin server, but comes from a local or third-party copy. This is mostly used for mirroring or backups of another resource. Except in this specific case, the 200 OK response is preferable to this status.
204 No Content
There is no content to send for this request, but the headers may be useful. The user agent can update its cached headers for this resource with the new headers.
205 Reset Content
Instructs the user agent to reset the document that sent this request.
206 Partial Content
This response code is used when the Range header is sent by the client to request only part of a resource.
207 Multi-Status (WebDAV)
Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
208 Already Reported (WebDAV)
Used within a
226 IM Used (HTTP Delta encoding)
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.
Redirection Messages
300 Multiple Choices
The request has more than one possible answer. The user agent or user should choose one of them. (There is no standardized way to select one of the answers, but HTML links to the possibilities are recommended so the user can choose.)
301 Moved Permanently
The URL of the requested resource has been permanently changed. The new URL is provided in the response.
302 Found
This response code means that the URI of the requested resource has been temporarily changed. Further changes to the URI may be made in the future, so the client should use the same URI in future requests.
303 See Other
The server sent this response to instruct the client to retrieve the requested resource at a different URI using a GET request.
304 Not Modified
This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
305 Use Proxy Deprecated
Was defined in a previous version of the HTTP specification to indicate that a requested response must be accessed through a proxy. Due to security concerns related to in-band configuration of a proxy, this option is deprecated.
306 unused
This response code is no longer used; it is merely reserved. It was used in an earlier version of the HTTP/1.1 specification.
307 Temporary Redirect
The server sends this response to instruct the client to obtain the requested resource at a different URI using the same method that was used in the previous request. This has the same semantics as the 302 Found HTTP response code, except that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
308 Permanent Redirect
This means that the resource is now permanently located at a different URI specified by the Location: HTTP response header. This has the same semantics as the 301 Moved Permanently HTTP response code, except that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
Client error responses
400 Bad Request
The server cannot or will not process the request because it considers it a client error (e.g., malformed request syntax, invalid request message framing, or misleading request routing).
401 Unauthorized
Although the HTTP standard specifies “unauthorized,” semantically this response means “unauthenticated.” That is, the client must authenticate to receive the requested response.
402 Payment Required (Experimental)
This response code is reserved for future use. Originally, this code was intended to be used for digital payment systems, but this status code is very rarely used and there is no standard convention.
403 Forbidden
The client does not have access rights to the content, i.e. it is not authorized, so the server cannot provide the requested resource. Unlike 401 Unauthorized, the identity of the client is known to the server.
404 Not Found
The server cannot find the requested resource. In the browser, this means that the URL is not recognized. In an API, it can also mean that the endpoint is valid, but the resource itself does not exist. Servers can also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well-known because it is common on the web.
405 Method Not Allowed
The request method is known to the server, but is not supported by the target resource. For example, an API may not allow calling DELETE to remove a resource.
406 Not Acceptable
This response is sent when the web server cannot find any content that matches the criteria specified by the user agent after server-directed content negotiation.
407 Proxy Authentication Required
This is similar to 401 Unauthorized, but authentication must be done through a proxy.
408 Request Timeout
This response is sent by some servers on an unused connection, even without a prior request from the client. It means that the server wants to close this unused connection. This response is more commonly used because some browsers, such as Chrome, Firefox 27+ or IE9, use HTTP pre-connection mechanisms to speed up browsing. Also note that some servers just close the connection without sending this message.
409 Conflict
This response is sent when a request conflicts with the current state of the server.
410 Gone
This response is sent when the requested content has been permanently deleted from the server without a redirect address. Clients are expected to clear their caches and links to the resource. The HTTP specification specifies that this status code should be used for “time-limited, promotional services”. APIs should not feel compelled to use this status code to indicate deleted resources.
411 Length Required
The server rejected the request because the Content-Length header field is not defined and the server requires it.
412 Precondition Failed
The client specified preconditions in its headers that the server does not meet.
413 Payload Too Large
The request unit is larger than the limits set by the server. The server may close the connection or return a Retry-After header field.
414 URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415 Unsupported Media Type
The media format of the requested data is not supported by the server, so the server rejects the request.
416 Range Not Satisfiable
The range specified in the Range header field of the request cannot be satisfied. It is possible that the range is outside the size of the target URI’s data.
417 Expectation Failed
This response code means that the expectation specified in the Expect header field of the request cannot be satisfied by the server.
418 I’m a teapot
The server rejects the attempt to brew coffee using a teapot.
421 Misdirected Request
The request was directed to a server that is unable to provide a response. This may be sent by a server that is not configured to produce responses for the combination of schema and authority contained in the request URI.
422 Unprocessable Content (WebDAV)
The request was well-formed, but could not be followed due to semantic errors.
423 Locked (WebDAV)
The resource being accessed is locked.
424 Failed Dependency (WebDAV)
The request failed because a previous request failed.
425 Too Early Experimental
Indicates that the server is not willing to risk processing a request that may be retried.
426 Upgrade Required
The server refuses to process the request using the current protocol, but may be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to specify the required protocol(s).
428 Precondition Required
The origin server requires that the request be conditional. This response is intended to prevent the “lost update” problem, where a client GETs the state of a resource, modifies it, and PUTs it back to the server, while a third party has modified the state on the server, causing a conflict.
429 Too Many Requests
The user has sent too many requests in a given time (“rate limiting”).
431 Request Header Fields Too Large
The server is not ready to process the request because its header fields are too large. The request can be resent after reducing the size of the request header fields.
451 Unavailable For Legal Reasons
The user agent has requested a resource that cannot be made available for legal reasons, such as a government-censored website.
Server Error Responses
500 Internal Server Error
The server encountered a problem that it cannot handle.
501 Not Implemented
The request method is not supported by the server and cannot be serviced. The only methods that servers must support (and therefore must not return this code) are GET and HEAD.
502 Bad Gateway
This error response means that the server acting as a gateway to receive a response required to service the request received an invalid response.
503 Service Unavailable
The server is unable to service the request. Common causes include a server that is down for maintenance or overloaded. Note that a user-friendly page explaining the problem should be sent along with this response. This response should be used for transient conditions, and the Retry-After HTTP header should, if possible, include the estimated time until service is restored. The webmaster must also pay attention to the caching headers sent along with this response, as these responses to transient conditions should normally not be cached.
504 Gateway Timeout
This error response is given when the server is acting as a gateway and cannot receive a response in a timely manner.
505 HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
506 Variant Also Negotiates
The server has an internal configuration error: the chosen variant resource is configured to perform transparent content negotiation itself, and is therefore not a proper endpoint in the negotiation process.
507 Insufficient Storage (WebDAV)
The method could not be executed on the resource because the server is unable to store the representation required to successfully complete the request.
508 Loop Detected (WebDAV)
The server encountered an infinite loop while processing the request.
510 Not Extended
The server needs additional extensions to fulfill the request.
511 Network Authentication Required
Indicates that the client must authenticate to gain access to the network.