HTTP Status Codes Reference
Developer References100% Client-SideComprehensive, searchable cheat sheet of all standard HTTP response status codes with detailed explanations.
Client should continue with its request.
Server is switching protocols (e.g. WebSocket handshake).
The request has succeeded.
Resource has been successfully created.
Request accepted for background processing.
Request succeeded, but no content in response body.
Resource permanently moved to a new URL.
Resource temporarily moved to a new URL.
Cached version is up to date (conditional GET).
Redirect maintaining same HTTP method.
Permanent redirect maintaining same HTTP method.
Malformed request syntax or validation error.
Authentication is required or invalid.
Authenticated, but access is not allowed.
Resource could not be found.
HTTP method not supported for resource.
Request conflicts with current state of resource.
Semantic errors in request body.
Rate limit exceeded.
Unexpected server error.
Invalid response from upstream backend server.
Server is overloaded or down for maintenance.
Upstream server failed to respond in time.
What is HTTP Status Codes Reference?
Complete reference guide of all standard IANA HTTP status codes categorized into 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Errors), and 5xx (Server Errors).
Key Features
Common Use Cases
- Choosing appropriate HTTP status codes when designing RESTful APIs
- Diagnosing web server errors (e.g. 502 Bad Gateway, 504 Gateway Timeout)
- Understanding client authentication errors (401 Unauthorized vs 403 Forbidden)