HTTP header parser

Paste response headers and read what Cache-Control, Set-Cookie, CSP and the others mean.

Runs in your browser. Your input is not uploaded.

Correctness last checked 2026-11-13. How we verify

What it does, how to use it, and questions

What it does

An HTTP response starts with a status line and then Name: value headers. A few of them decide caching, cookies, framing and what the browser is allowed to load.

This parser names those headers and spells out the directives it recognises. A header it does not know is shown as sent, with no invented meaning.

How to use it

  1. Paste the status line and headers, or the headers alone.
  2. Read the note under each header.
  3. A line without a colon is reported with its line number.

Example

Input
Cache-Control: public, max-age=60
Output
public: a shared cache may store this. max-age=60: a browser may reuse this response for 60 seconds.

Things to watch for

  • Folded header lines (a continuation that starts with a space) are joined. A header split that way is one header.
  • The CSP note lists the directive names. It does not judge whether the policy is strict enough.
  • Set-Cookie can appear more than once. Each one is listed separately.

Questions

What does Cache-Control: no-cache mean?
A cache may store the response, but it must check with the origin before using it. no-store is the one that forbids storing it.
What does SameSite=Lax do?
The browser sends the cookie on a normal navigation from another site, and withholds it from cross-site subrequests such as images and fetches.
Does this fetch the URL?
No. Paste the headers you already have. Nothing is requested.
Why is a header marked with no extra note?
It is not one of the headers this page explains. The value is still shown unchanged.