Browse all HTTP status codes. Search by code number, name, or description.
100% client-side processing
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, for example upgrading from HTTP to WebSocket.
The server has received and is processing the request, but no response is available yet (WebDAV).
Used to return some response headers before the final HTTP message, allowing the client to preload resources.
The request has succeeded. The meaning depends on the HTTP method (GET, POST, PUT, DELETE, etc.).
The request has been fulfilled and resulted in a new resource being created, typically after a POST request.
The request has been accepted for processing but the processing has not been completed yet.
The returned metadata may be from a third-party copy rather than the origin server.
The server successfully processed the request and is not returning any content body.
The server successfully processed the request and asks the client to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
The request has more than one possible response. The user or user agent should choose one of them.
The URL of the requested resource has been changed permanently. The new URL is given in the response.
The requested resource resides temporarily under a different URI. The client should continue to use the original URI.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Indicates that the resource has not been modified since the version specified by the request headers (used for caching).
The server sends this response to direct the client to a different URI, but the client must use the same HTTP method.
The resource is now permanently located at another URI, and the client must use the same HTTP method for future requests.
The server cannot or will not process the request due to something that is perceived to be a client error (malformed syntax).
The client must authenticate itself to get the requested response. Often called "unauthenticated" rather than "unauthorized".
The client does not have access rights to the content; the server is refusing to give the requested resource.
The server can not find the requested resource. This is the most well-known HTTP error status code.
The request method is known by the server but is not supported by the target resource.
The server timed out waiting for the request from the client. The client may repeat the request without modifications.
The request could not be completed due to a conflict with the current state of the target resource.
The requested content has been permanently deleted from the server, with no forwarding address.
The request entity is larger than limits defined by the server; the server might close the connection or return a Retry-After header.
The URI requested by the client is longer than the server is willing to interpret.
The media format of the requested data is not supported by the server, so the server is rejecting the request.
The server refuses the attempt to brew coffee with a teapot. This is an April Fools joke from RFC 2324 (HTCPCP).
The request was well-formed but was unable to be followed due to semantic errors (WebDAV).
The user has sent too many requests in a given amount of time ("rate limiting"). The response should include a Retry-After header.
The server is denying access to the resource as a consequence of a legal demand (e.g., censorship or copyright).
The server has encountered a situation it does not know how to handle. This is a generic server error response.
The request method is not supported by the server and cannot be handled. The server either does not recognize the request method or lacks the ability to fulfill it.
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
The server is not ready to handle the request. Common causes are server maintenance or temporary overloading.
The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
No status codes found matching your search.