Delimiter.live
Developer Tools Runs in your browser Free · no account

HTTP Header Parser

The HTTP header parser takes a raw request or response header block — the kind you copy out of curl, developer tools or a log — and splits it into a table of names and values. It recognises the request or status line and joins folded continuation lines back together.

Raw headers 0 characters
Headers

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the HTTP Header Parser

  1. Copy the raw header block from curl -i, your browser developer tools or a log.
  2. Paste it in — the request or status line on the first line is recognised automatically.
  3. Read the parsed table.

Example

Input
HTTP/1.1 200 OK
Content-Type: text/html
Output
Content-Type | text/html

Common use cases

  • Reading a header block pasted into a bug report or support ticket.
  • Checking which cache and security headers a response actually carried.
  • Comparing the headers from two environments line by line.
  • Making a long Set-Cookie or Content-Security-Policy value readable.

Limitations and things to watch for

  • This parses text you paste; it does not fetch anything. To see the headers a live URL returns, use the HTTP Header Checker, which makes the request from our server.
  • Values are not interpreted. A Content-Security-Policy is shown as one long string rather than being broken into directives.
  • Header names are case-insensitive in HTTP, so they are shown exactly as pasted rather than being normalised.

Frequently asked questions

How is this different from the HTTP Header Checker?
This tool parses a block you already have, entirely in your browser. The HTTP Header Checker takes a URL and fetches it from our server to find out what it returns. Use this one when you have already captured the headers.
What is a folded header?
An older convention where a long value continued on the next line, indented by a space. It is deprecated in current HTTP but still appears in email headers and older logs, so continuation lines are joined back onto the header above.
Does it handle both request and response headers?
Yes. A request line such as GET /path HTTP/1.1 and a status line such as HTTP/1.1 200 OK are both recognised and shown separately from the headers themselves.
Is the header block sent anywhere?
No. Parsing runs in your browser, which matters because header blocks frequently contain cookies, authorisation tokens and session identifiers.

Share this tool