Library Mini-game · 10 roundsWhich status code?Watch the request, pick the code.Start the track
HTTP status codes
Which box sends each code, and why. You watch the request cross the stack and see which box answers: the browser, the CDN, the proxy or the app.
1xx / 2xx · it worked
The request was understood and handled.
3xx · look somewhere else
The answer is at another URL, or already in your cache.
- 301Moved PermanentlyThis address has moved for good. Use the new one in the Location header from now on.
- Browser
- CDN
- Proxy
- App
- DB
- 302FoundWhat you asked for is at another address for now. Keep using the original address next time.
- Browser
- CDN
- Proxy
- App
- DB
- 304Not ModifiedYour cached copy is still current. Use it; no body is sent.
- Browser
- CDN
- Proxy
- App
- DB
- 307Temporary RedirectGo to another address for now, and repeat the request there exactly: same method, same body.
- Browser
- CDN
- Proxy
- App
- DB
- 308Permanent RedirectThis address has moved for good, and requests must be repeated at the new one unchanged.
- Browser
- CDN
- Proxy
- App
- DB
4xx · the request is the problem
Sending the same request again will get the same answer.
- 400Bad RequestThe server could not make sense of the request itself, so it did not try to act on it.
- Browser
- CDN
- Proxy
- App
- DB
- 401UnauthorizedThe server does not know who you are. Send valid credentials and try again.
- Browser
- CDN
- Proxy
- App
- DB
- 403ForbiddenThe server understood the request and refuses it. Logging in again will not help.
- Browser
- CDN
- Proxy
- App
- DB
- 404Not FoundThe server has nothing at this address, or is not willing to say that it does.
- Browser
- CDN
- Proxy
- App
- DB
- 405Method Not AllowedThe address exists, but it does not accept this method. The Allow header lists the ones it does.
- Browser
- CDN
- Proxy
- App
- DB
- 409ConflictThe request is valid, but it clashes with the current state of the thing it wants to change.
- Browser
- CDN
- Proxy
- App
- DB
- 413Content Too LargeThe request body is bigger than the server is willing to accept.
- Browser
- CDN
- Proxy
- App
- DB
- 422Unprocessable ContentThe request is well formed and understood, but its contents do not make sense to act on.
- Browser
- CDN
- Proxy
- App
- DB
- 429Too Many RequestsYou have sent more requests than allowed in a period of time. Slow down and try later.
- Browser
- CDN
- Proxy
- App
- DB
- 499Client Closed RequestNon-standardThe client gave up and closed the connection before the server had answered. Nobody receives this code.
- Browser
- CDN
- Proxy
- App
- DB
5xx · the server side is the problem
The request was fine. Something behind it was not.
- 500Internal Server ErrorThe server hit something it did not expect and could not finish the request.
- Browser
- CDN
- Proxy
- App
- DB
- 502Bad GatewayA proxy passed your request on and got back something that was not a valid response.
- Browser
- CDN
- Proxy
- App
- DB
- 503Service UnavailableThe server is up but is refusing work for now, because it is overloaded or in maintenance.
- Browser
- CDN
- Proxy
- App
- DB
- 504Gateway TimeoutA proxy passed your request on, waited, and gave up before the server behind it answered.
- Browser
- CDN
- Proxy
- App
- DB
Edge / CDN · vendor codes
Non-standard codes invented by one vendor.
Codes people mix up
The same request, played side by side, so the difference shows in a few seconds.
- 301 vs 302301: moved for good, and clients may remember it. 302: somewhere else for now, so ask again next time.
- 307 vs 308Both repeat the request unchanged. 307 is temporary; 308 is permanent and may be remembered.
- 400 vs 422400: the server could not read the request. 422: it read it fine, and the contents are not acceptable.
- 401 vs 403401: the server does not know who you are. 403: it knows, and the answer is still no.
- 500 vs 503500: the server tried and broke. 503: the server chose not to try right now.
- 502 vs 503 vs 504502: the proxy got a broken answer. 503: something said “not now”. 504: the proxy got no answer in time.
Practise this in the DNS / HTTP track
Two-minute animated lessons, then boss fights from real outages. Free, no account needed.