Web Platform
Searchable reference for HTTP status codes with descriptions and common causes.
Showing 32 of 32 status codes
The server has received the request headers and the client should proceed to send the request body.
The server is switching to the protocol requested by the client, such as upgrading from HTTP/1.1 to WebSocket.
The request succeeded. This is the standard response for successful HTTP requests.
The request succeeded and a new resource was created. Typically returned after POST or PUT requests.
The request has been accepted for processing, but the processing has not been completed yet.
The server successfully processed the request but is not returning any content. Often used for DELETE operations.
The server is delivering only part of the resource due to a Range header sent by the client.
The resource has been permanently moved to a new URL. Search engines will update their links to the new location.
The resource is temporarily located at a different URL. The client should continue to use the original URL for future requests.
The response to the request can be found at another URL using a GET method. Often used after a POST to redirect to a result page.
The resource has not been modified since the last request. The client can use its cached version.
The resource is temporarily at a different URL. Unlike 302, the request method must not change when following the redirect.
The resource has permanently moved to a new URL. Unlike 301, the request method must not change when following the redirect.
The server cannot process the request due to malformed syntax, invalid parameters, or other client-side errors.
Authentication is required to access the resource. The client must provide valid credentials.
The server understood the request but refuses to authorize it. Authentication will not help.
The requested resource could not be found on the server. This is the most common error encountered on the web.
The HTTP method used is not supported for the requested resource. For example, using POST on a read-only endpoint.
The server timed out waiting for the client to complete the request. The client may retry without modifications.
The request conflicts with the current state of the server, such as editing a resource that was modified by another user.
The resource is no longer available and has been permanently removed. Unlike 404, this indicates intentional removal.
The request payload exceeds the size limit defined by the server. The client should reduce the request size.
The request URI is longer than the server is willing to interpret. This often happens with overly long query strings.
The server refuses the request because the payload format is not supported. Check the Content-Type header.
An April Fools joke from RFC 2324. The server refuses to brew coffee because it is a teapot.
The server understands the content type but cannot process the contained instructions. Often used for validation errors.
The user has sent too many requests in a given amount of time. Used for rate limiting.
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 method may not be recognized.
The server acting as a gateway received an invalid response from the upstream server.
The server is temporarily unable to handle the request due to maintenance or overload. Try again later.
The server acting as a gateway did not receive a timely response from the upstream server.
Convert timestamps to readable dates and switch between common time formats.
Compose Content Security Policy directives locally and inspect the resulting header.
Convert colors between hex, RGB, HSL, and OKLCH formats with a live swatch preview.