About

Tool No. 47 of Pikkola

Most debugging happens in the gap between what a server meant to send and what the browser actually read. This page puts the two sides next to each other: a reference for the code, a builder for the headers, and a parser that reads a real response back.

What it does

How retry and cache are decided

Retry answers a narrow question: may a client send the same request again without asking anyone? 408, 425, 429 and 502 to 504 are marked yes, because the request reached a server that could not finish it and nothing in the request is known to be wrong. 409, 412 and 500 are marked conditional: a retry is correct after the client re-reads the state or attaches an idempotency key, and wrong before that.

Cache answers whether a response may be reused at all by default. 200, 203, 204, 206 and 301 may be. 404, 405, 410 and 501 are heuristically cacheable, which is why a deleted page can stay away for a while even with no cache header. 302, 307 and 308 depend on what the response says, so the table marks them as needing a header. A 5xx is never reused.

Why the builder warns

Every warning here is a combination that fails in a real browser or a real cache, not a preference. A wildcard origin with credentials is rejected outright. SameSite=None without Secure is rejected outright. A public response with Set-Cookie may be stored with the cookie inside. A preflight answer over 7200 seconds is quietly capped by Chrome. The row tells you which of those you have.

The preview is what the server should send; the snippets are the same intent written for four servers. They differ on purpose, because Nginx drops outer add_header lines in a location that has its own, Caddy replaces an app's Set-Cookie when it sets one, and a Worker has to copy headers onto a new Response. The note under each snippet says what to watch.

What the parser judges

It reads what came back: HSTS and its max-age, a policy that still allows unsafe-inline, a nosniff that says something else, a frame rule missing on both sides, a referrer policy that passes the full address, a cookie without HttpOnly, a wildcard origin with credentials, a server header carrying a version. Missing headers are named too, because a page without a policy is the most common finding of all.

It judges only the response. It cannot know what your app meant to send, whether a route exists, why an origin answered 502, or whether the HTML would break a stricter policy. Those need the request, the logs and a person.

What it deliberately does not do

Why it is free

Pikkola builds small tools that do one job and keeps them free, with no account and no advertising. A static page that computes in the browser costs almost nothing to serve, so there is no reason to charge for it.

Contact

A status code described wrongly, a header check that should exist, a snippet that breaks on your server: hello@pikkola.com. Send the response headers you pasted and what you expected to see.

Back to the studio