Available images
This interim response indicates that the client should continue the request or ignore the response if the request is already finished.
[MDN]This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.
[MDN]This code was used in WebDAV contexts to indicate that a request has been received by the server, but no status was available at the time of the response.
[MDN]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 or preconnect to an origin from which the page will need resources.
[MDN]The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.
[MDN]The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.
[MDN]This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the 200 OK response is preferred to this status.
[MDN]The server sends this response to direct the client to get the requested resource at another URI with the same method that was used in the prior request. This has the same semantics as the 302 Found response code, with the exception 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 redirected request.
[MDN]The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
[MDN]Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
[MDN]The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
[MDN]The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may 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 due to its frequent occurrence on the web.
[MDN]This is similar to 401 Unauthorized but authentication is needed to be done by a proxy.
[MDN]The request body is larger than limits defined by server. The server might close the connection or return a Retry-After header field.
[MDN]This response code means the expectation indicated by the Expect request header field cannot be met by the server.
[MDN]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 server sends an Upgrade header in a 426 response to indicate the required protocol(s).
[MDN]The user has sent too many requests in a given amount of time (rate limiting).
[MDN]The user agent requested a resource that cannot legally be provided, such as a web page censored by a government.
[MDN]The server has encountered a situation it does not know how to handle. This error is generic, indicating that the server cannot find a more appropriate 5XX status code to respond with.
[MDN]The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
[MDN]