Back to Free Tools
FREE TOOLS
Raw HTTP Message Parser
Inspect one byte-exact HTTP/1.1 UTF-8 message file with strict CRLF, length framing and ordered header reporting.
Raw HTTP/1.1 UTF-8 message file
JSON message report
Browser only
Runs locally in your browser. Your files, pasted content and generated output are not uploaded. Reset clears this tool’s working data.
This tool needs JavaScript. If it does not load, refresh the page and try again.
How to use this tool
- Choose Raw HTTP/1.1 UTF-8 message file. There is no pasted-text route because textarea normalization cannot preserve wire CRLF bytes.
- Choose Response request context GET or HEAD; this setting is ignored for request snapshots. Origin-form requests and OPTIONS * are supported.
- Select Inspect HTTP message snapshot and download http-message.json. Raw ordered header values and exact body octet count are retained.
Examples
A body containing é needs Content-Length:2. HEAD/304 can carry representation length metadata while their wire body stays empty.
Limitations
- One file up to 5 MiB; header section256 KiB,1,000 headers,8,192 bytes per start/header line,20 MiB JSON and 30 seconds. Whole-file BOM is rejected; body BOM is data.
- Rejects all Transfer-Encoding, duplicate Content-Length, obs-fold, nonidentity Content-Encoding, CONNECT/upgrades, close-delimited responses, pipeline/extra/truncated bytes and malformed UTF-8.
- Body C0 controls except tab/CR/LF and DEL are excluded by this text subset. HEAD/304 are bodyless; 1xx/204 also forbid Content-Length.
- No arbitrary binary or multipart decoder, HTTP2/3, network send or security/smuggling certification. Generic broader HTTP source coverage remains partial.
Related tools
No items found.