Loona Automation logoLoona Developer Tools
Home › Reference

HTTP Status Codes Reference

In short: all the status codes that matter in daily development — what each one means, when it is used, and the traps (401 vs 403, 302 vs 307) — filterable as you type.
🔒 Private by design: everything runs in your browser on this device. Your input is never uploaded to a server.
CodeNameMeaning
100ContinueClient should continue with the request body
101Switching ProtocolsProtocol upgrade accepted (e.g. to WebSocket)
200OKThe request succeeded — the default success response
201CreatedA new resource was created (typical POST success)
202AcceptedQueued for async processing, not yet complete
204No ContentSuccess with an intentionally empty body
301Moved PermanentlyResource has a new permanent URL — update links; SEO equity transfers
302FoundTemporary redirect (historically misused; see 303/307)
303See OtherRedirect to a GET at another URL (post/redirect/get)
304Not ModifiedCached copy is still valid — revalidate via ETag/Last-Modified
307Temporary RedirectTemporary redirect preserving method and body
308Permanent RedirectPermanent redirect preserving method and body
400Bad RequestThe server cannot parse/understand the request
401UnauthorizedAuthentication required or failed (despite the name, it means unauthenticated)
403ForbiddenAuthenticated or not, access is refused
404Not FoundNo resource at this URL
405Method Not AllowedThe HTTP method is not supported for this resource
406Not AcceptableNo representation matches the Accept headers
408Request TimeoutThe client took too long to send the request
409ConflictState conflict, e.g. edit collision or duplicate creation
410GonePermanently removed (stronger than 404 — used deliberately)
411Length RequiredContent-Length header is required
413Content Too LargeRequest body exceeds server limits
414URI Too LongThe URL exceeds server limits
415Unsupported Media TypeThe request Content-Type is not supported
418I'm a TeapotRFC 2324 joke code, occasionally used to refuse brewing coffee
422Unprocessable ContentSyntax is fine but semantics fail validation (APIs love this one)
425Too EarlyServer unwilling to process a possibly-replayed request
429Too Many RequestsRate limit hit — back off, honour Retry-After
500Internal Server ErrorGeneric server-side failure
501Not ImplementedThe server does not support the functionality
502Bad GatewayA proxy/gateway got an invalid response from upstream
503Service UnavailableOverloaded or down for maintenance — often temporary, may carry Retry-After
504Gateway TimeoutA proxy/gateway timed out waiting for upstream
505HTTP Version Not SupportedThe 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).

Related Developer Tools

Embed this tool on your website — free

Add this tool to your own website or blog — it is completely free, needs no sign-up, and always shows the latest version. Copy the code below and paste it into your page where you want the tool to appear. Keeping the small “Powered by Loona Automation” credit line under the embed helps keep this tool free — but you are free to style or remove it; the tool works either way.