HTTP Status Codes

The 40 status codes a working developer actually encounters — what they mean, when they fire, and how to tell similar codes apart.

  • 40 cards
  • English
  • $0.99
Get Hanase Browse the catalog →

The 40 status codes a working developer actually encounters — what they mean, when they fire, and how to tell similar codes apart.

Hanase delivers each card as a quiet notification; one tap reveals the answer. A little, often — until it’s yours. It’s a one-time $0.99 purchase — no subscription.

A look inside

A few of the 40 cards in this pack — front, then what one tap reveals.

100
Continue
Informational
Meaning Initial part of request received; client should continue sending the body.
When After the client sends an "Expect: 100-continue" header on a large request, the server signals it's ready to receive the body.
Note Most modern HTTP libraries handle this handshake transparently.
101
Switching Protocols
Informational
Meaning Server is switching to a different protocol (e.g. HTTP/1.1 → WebSocket).
When The handshake response when a client requests a connection upgrade via the Upgrade header.
Note The first response you'll see in any WebSocket connection.
103
Early Hints
Informational
Meaning Hints that let the client start preloading resources before the final response.
When Modern browsers can begin fetching CSS/JS while the server is still computing the main response body.
Note Newer standard (RFC 8297, 2017). CDNs like Cloudflare emit it; broader adoption is still spreading.
200
OK
Success
Meaning Standard successful response.
When Most GET requests return this when everything went right.
Compare 204 No Content is similar but carries no response body.
201
Created
Success
Meaning A new resource was created as a result of the request.
When After a successful POST that creates an entity. Response should include a Location header pointing at the new resource.
Compare 200 for non-creating successes; 202 for "queued but not yet created".
202
Accepted
Success
Meaning Request accepted for processing, but the work isn't complete.
When Async operations — the server queued the task. Client should poll for status or wait for a webhook.
Compare 201 means "done, here's the resource"; 202 means "we'll get there".

How Hanase teaches it

Cards don't wait in a deck for you to open them. One arrives as a gentle notification; a glance shows the prompt, one tap reveals the answer. It works on iPhone, iPad, Mac, and Apple Watch, and there are no streaks, scores, or shame — just a little, often, until it's yours.

More English

E
English — A1
149 cards · Free
E
English — A2
151 cards · Free
E
English — B1 Vocabulary I
149 cards · In Intermediate English
E
English — B1 Vocabulary II
149 cards · In Intermediate English
E
English — B1 Vocabulary III
149 cards · In Intermediate English
E
English — B2 Vocabulary I
149 cards · In Advanced English

Questions

What’s in the HTTP Status Codes pack?
The 40 status codes a working developer actually encounters — what they mean, when they fire, and how to tell similar codes apart. 40 cards in all.
Which devices does it work on?
Hanase runs on iPhone, iPad, Mac, and Apple Watch. Cards arrive as gentle notifications and your progress syncs across your devices over iCloud.
Does it work offline?
Yes. Once a pack is downloaded the cards live on your device, so reviews keep arriving with no connection.
How much does it cost?
It’s a one-time $0.99 purchase. Hanase has no subscription — you buy a pack once and keep it.

Learn http status codes in the in-between.

Get Hanase — free