Pikkola Network Studio, tool No. 47

Read the response the way the browser does.

Three rooms: a status code reference you can search by symptom, a CORS and cache header builder with the warnings browsers actually enforce, and a parser that reads back the headers a real response arrived with.

40
status codes
0
requests sent
EN / KO / JA
three languages

The three rooms

Look it up, build it, read it back

One tab answers what a code means. One builds the headers a server should send. One takes the headers a server did send and says what is missing. Nothing leaves the tab.

Every code a browser will hand you

Search by number, by name, or by the symptom in front of you. Retry and cache say what a client may do without asking anyone, and every code carries the move for each side of the wire.

40 of 40 codes

Class
Retry
Cache

How it reads

Three things a header cannot say on its own

A header is a promise about a response, not the response itself. Knowing where the promise and the fact part company is the whole job.

01

A header is half an instruction

A header travels with a response, never before it. The builder shows what a server should send; the parser shows what it did send. The two do not always agree, and the gap between them is the bug.

02

Browsers are stricter than the spec

A wildcard origin with credentials, SameSite=None without Secure, immutable on a short max-age: the words may be legal and the combination is still refused. The checks here are the ones that surface as a blocked request or a cookie that never arrives.

03

A response is not a request

The parser reads what came back, so it judges only that. It cannot know what your app meant to send, whether the route exists, or why an origin answered 502. It tells you which promises this response kept.

The three rooms, one row each
Room Takes Gives back
Status codes A number, a name, or a symptom Meaning, cause, and the next move for each side
Header builder Switches and values The header block and four server snippets
Header parser Raw response headers Each header judged, and the ones that are missing

Questions

Why is a wildcard origin rejected when cookies are sent?

Because a wildcard would let any site read a response that carries the person's session. The browser blocks it and asks for a named origin. The builder flags the pair before you deploy, and the parser flags it in a live response.

Is a 200 always a success?

For the transport, yes. For the meaning, no. A 200 with an error object in the body is a common API habit, and a 204 that carries a body is malformed. Read the body, not only the status line.

Should a static asset ever be no-store?

Not if its URL changes when the file changes. A fingerprinted asset wants a year and immutable, an HTML page wants revalidation, and a private API answer wants no-store. Mixing them is where a cached login shows up.

Does the parser fetch anything?

No. It reads the text you paste. The page's own content policy sets connect-src to none, so no request could leave even if the code tried to make one.

Are the snippets ready to paste?

They have the right shape for each server and this builder's values. Nginx, Workers and Express scope headers differently, and Caddy replaces Set-Cookie when it sets one, so read the note under each snippet before you deploy.

Which codes may a client retry?

408, 425, 429 and 502 to 504 are safe with backoff, and the table marks them. A write needs an idempotency key before any retry, because a timeout does not mean the work did not happen.