HTTP Status Codes
Every status code from 100 to 511, searchable and explained.
Processed in your browser
Your entered content is processed on this device. It is not uploaded by this tool. Some tools load code or public resources before processing.
1xx - Informational
Keep going - the server got the headers and the client should send the body.
The server is switching protocols as requested, e.g. upgrading to WebSockets.
WebDAV: received and working on it, no response yet.
Preload hints sent before the final response arrives.
2xx - Success
The classic. Request succeeded, response body has the goods.
A new resource was created - POST and PUT’s happy ending.
Queued for processing; it hasn’t actually happened yet.
Success, but nothing to send back. Common for DELETE.
A byte-range slice of the resource - how video streaming and resumable downloads work.
3xx - Redirection
Gone for good - update your links. Browsers cache this aggressively.
Temporary redirect; keep using the original URL next time.
Your cached copy is still fresh - no body sent. The backbone of HTTP caching.
Like 302 but the method must not change (POST stays POST).
Like 301 but the method must not change.
4xx - Client errors
The server can’t parse what you sent - malformed syntax or invalid framing.
Really means unauthenticated: no valid credentials supplied.
Authenticated, but you’re still not allowed. The server knows who you are and the answer is no.
Nothing lives at this URL. The internet’s most famous number.
The URL exists but not for that verb - e.g. POSTing to a GET-only endpoint.
The request clashes with current state - edit collisions, duplicate creates.
Existed once, deliberately removed, never coming back. A 404 with closure.
RFC 2324, April 1st 1998. The server refuses to brew coffee because it is, permanently, a teapot.
Well-formed request, invalid semantics - validation errors live here.
Rate limited. Check the Retry-After header and calm down.
5xx - Server errors
Something broke server-side and it isn’t saying what. Check the logs.
The server doesn’t support the functionality required to fulfil this.
A proxy/load balancer got a garbage response from the app behind it.
Overloaded or down for maintenance. Usually temporary, often with Retry-After.
The upstream took too long to answer the proxy in front of it.
Log in to the captive portal first - hello, airport wifi.