HTTP Status Code Reference
Look up HTTP status codes with descriptions, use cases, and examples.
The server has received the request headers and the client should proceed to send the request body.
Use case: Used in POST requests with large bodies; client checks if server will accept before sending.
The server agrees to switch protocols as requested by the client.
Use case: WebSocket upgrade from HTTP to WS protocol.
The server has received and is processing the request, but no response is available yet.
Use case: Long-running operations to prevent client timeout.
Used to return some response headers before final HTTP message.
Use case: Preloading resources before the main response is ready.
The request succeeded. The meaning depends on the HTTP method used.
Use case: Standard success response for GET, POST, PUT requests.
The request succeeded and a new resource was created as a result.
Use case: Returned after a successful POST that creates a new resource.
The request has been accepted for processing, but processing has not been completed.
Use case: Async operations where processing happens in background.
The server successfully processed the request and is not returning any content.
Use case: DELETE requests, or PUT/PATCH with no response body needed.
The server is delivering only part of the resource due to a Range header sent by the client.
Use case: Video streaming, resumable file downloads.
The requested resource has been permanently moved to a new URL.
Use case: Permanent redirects; SEO-friendly for URL changes.
The resource is temporarily under a different URI.
Use case: Temporary redirects, login redirects.
The resource has not been modified since the last request.
Use case: Browser caching; server confirms cached version is still valid.
The request should be repeated with another URI but future requests can still use the original URI.
Use case: Temporary redirect that preserves the HTTP method.
The request and all future requests should be repeated using another URI.
Use case: Permanent redirect that preserves the HTTP method.
The server could not understand the request due to invalid syntax.
Use case: Malformed JSON, missing required fields, invalid parameters.
The client must authenticate itself to get the requested response.
Use case: Missing or invalid authentication token.
The client does not have access rights to the content.
Use case: Authenticated but not authorized; access denied to resource.
The server can not find the requested resource.
Use case: Invalid URL, deleted resource, or hidden resource.
The request method is known by the server but is not supported by the target resource.
Use case: POST to a read-only endpoint, DELETE on non-deletable resource.
The server would like to shut down this unused connection.
Use case: Client took too long to send a complete request.
The request conflicts with the current state of the server.
Use case: Duplicate resource creation, version conflicts.
The requested content has been permanently deleted from the server.
Use case: Deliberately removed resources; stronger signal than 404.
The request was well-formed but was unable to be followed due to semantic errors.
Use case: Validation errors β correct format but invalid data.
The user has sent too many requests in a given amount of time (rate limiting).
Use case: API rate limiting, DDoS protection.
The server encountered an unexpected condition that prevented it from fulfilling the request.
Use case: Unhandled exceptions, server-side bugs.
The server does not support the functionality required to fulfill the request.
Use case: HTTP method not recognized or supported by server.
The server, while acting as a gateway, received an invalid response from an upstream server.
Use case: Reverse proxy issues, upstream server errors.
The server is not ready to handle the request.
Use case: Server maintenance, overloaded server.
The server is acting as a gateway and cannot get a response in time.
Use case: Upstream server too slow, network timeouts.
The HTTP version used in the request is not supported by the server.
Use case: Client using unsupported HTTP version.
Comments & Feedback
Comments are powered by Giscus. Sign in with GitHub to leave a comment.