HTTP Status Codes Reference
| Code | Name | Meaning |
|---|---|---|
| 100 | Continue | Client should continue with the request body |
| 101 | Switching Protocols | Protocol upgrade accepted (e.g. to WebSocket) |
| 200 | OK | The request succeeded — the default success response |
| 201 | Created | A new resource was created (typical POST success) |
| 202 | Accepted | Queued for async processing, not yet complete |
| 204 | No Content | Success with an intentionally empty body |
| 301 | Moved Permanently | Resource has a new permanent URL — update links; SEO equity transfers |
| 302 | Found | Temporary redirect (historically misused; see 303/307) |
| 303 | See Other | Redirect to a GET at another URL (post/redirect/get) |
| 304 | Not Modified | Cached copy is still valid — revalidate via ETag/Last-Modified |
| 307 | Temporary Redirect | Temporary redirect preserving method and body |
| 308 | Permanent Redirect | Permanent redirect preserving method and body |
| 400 | Bad Request | The server cannot parse/understand the request |
| 401 | Unauthorized | Authentication required or failed (despite the name, it means unauthenticated) |
| 403 | Forbidden | Authenticated or not, access is refused |
| 404 | Not Found | No resource at this URL |
| 405 | Method Not Allowed | The HTTP method is not supported for this resource |
| 406 | Not Acceptable | No representation matches the Accept headers |
| 408 | Request Timeout | The client took too long to send the request |
| 409 | Conflict | State conflict, e.g. edit collision or duplicate creation |
| 410 | Gone | Permanently removed (stronger than 404 — used deliberately) |
| 411 | Length Required | Content-Length header is required |
| 413 | Content Too Large | Request body exceeds server limits |
| 414 | URI Too Long | The URL exceeds server limits |
| 415 | Unsupported Media Type | The request Content-Type is not supported |
| 418 | I'm a Teapot | RFC 2324 joke code, occasionally used to refuse brewing coffee |
| 422 | Unprocessable Content | Syntax is fine but semantics fail validation (APIs love this one) |
| 425 | Too Early | Server unwilling to process a possibly-replayed request |
| 429 | Too Many Requests | Rate limit hit — back off, honor Retry-After |
| 500 | Internal Server Error | Generic server-side failure |
| 501 | Not Implemented | The server does not support the functionality |
| 502 | Bad Gateway | A proxy/gateway got an invalid response from upstream |
| 503 | Service Unavailable | Overloaded or down for maintenance — often temporary, may carry Retry-After |
| 504 | Gateway Timeout | A proxy/gateway timed out waiting for upstream |
| 505 | HTTP Version Not Supported | The HTTP version in the request is not supported |
About
Status codes are the server's one-number summary of every response, grouped by class: 1xx informational, 2xx success, 3xx redirection, 4xx the client erred, 5xx the server erred. The table gives the codes working developers actually meet, with the nuances that matter in practice — 401 means unauthenticated despite its name, 403 is a refusal regardless of login, 422 is the API validation failure, 429 demands backoff. Codes not listed (the long tail of 1xx and experimental codes) are rare enough that the class alone tells you how to handle them.
Frequently Asked Questions
What is the difference between 401 and 403?
401: we do not know who you are (authenticate). 403: we know, and you still may not.
302 or 307 for a temporary redirect?
307 preserves the method and body; 302 historically let clients switch POST to GET. New work should use 307 (or 308 for permanent).