myfl.uk · status-code zoo

The HTTP status zoo

Every code below is real: visit /zoo/418 and the edge really returns 418 I'm a Teapot. Any code from 200–599 works, curated or not, for testing HTTP clients, webhooks and monitoring. JSON twin: /zoo/418.json.

2xx — success

CodeNameMeaning
200OKThe request succeeded. The menagerie's favourite.
201CreatedA new resource now exists.
202AcceptedReceived; processing happens later.
204No ContentSuccess with an intentionally empty body.
206Partial ContentA byte-range of the resource.

3xx — redirection

CodeNameMeaning
300Multiple ChoicesPick one of several representations.
301Moved PermanentlyRelocated for good (no Location header here).
302FoundRelocated for now.
304Not ModifiedUse your cached copy.
307Temporary RedirectTry again elsewhere, same method.
308Permanent RedirectRelocated for good, same method.

4xx — client error

CodeNameMeaning
400Bad RequestThe request made no sense.
401UnauthorizedAuthentication is missing or failed.
403ForbiddenUnderstood, but refused.
404Not FoundNothing lives here.
405Method Not AllowedWrong verb for the path.
406Not AcceptableNone of your acceptable types match.
408Request TimeoutYou took too long.
409ConflictThe resource is in a state clash.
410GoneIt existed, but no longer.
411Length RequiredA Content-Length is needed.
413Payload Too LargeToo heavy.
414URI Too LongThat URL is absurd.
415Unsupported Media TypeWrong content type.
418I'm a TeapotRFC 2324. Short and stout.
422Unprocessable EntityWell-formed, but semantically wrong.
425Too EarlyPatience; the server is still thinking.
426Upgrade RequiredSwitch protocols first.
429Too Many RequestsSlow down.
431Request Header Fields Too LargeThe headers got out of hand.
451Unavailable For Legal ReasonsWithheld by law. See RFC 7725.

5xx — server error

CodeNameMeaning
500Internal Server ErrorSomething broke server-side.
501Not ImplementedThis zoo does not do that.
502Bad GatewayAn upstream answered badly.
503Service UnavailableTemporarily away.
504Gateway TimeoutAn upstream took too long.
505HTTP Version Not SupportedAn ancient protocol.

Redirect codes return no Location header, so clients see the status without being auto-followed. 204 and 304 are body-less by spec. Back to the index.