ToolJovia
Developer

HTTP Message Framing Inspector

Inspect one supplied HTTP1 message and decode strictly bounded chunked content offline.

✓ Browser-local processing

Loading tool…

How to use HTTP Message Framing Inspector

Inspect one supplied HTTP1 message and decode strictly bounded chunked content offline. The parser separates a CRLF start line, headers and UTF8 body, rejects conflicting framing and verifies declared chunk/body lengths. It reports exactly what the supplied bytes contain without opening a connection.

  1. Provide escaped crlf text or utf8 message hex.
  2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
  3. Copy the result or download a separate output; reset to clear the current form.

Good to know

  • 100,000 characters,100 headers,1,000 chunks. Chunk extensions and transfer codings other than chunked are unsupported.
  • Choose escaped CRLF spelling (literal backslash-r-backslash-n is decoded) or strict UTF8 message hex; this avoids textarea newline normalization. UTF8 body text is counted as bytes. No HEAD/CONNECT context, connection completion, actual server parser behavior or request-smuggling result is inferred.
  • Inputs are processed on this device and are not automatically saved or uploaded.

Common questions

Why are LF-only messages rejected?

This workbench inspects explicit HTTP1 wire framing. It requires CRLF rather than silently changing a pasted message and hiding a framing difference.

Does this change my original input?

No. The tool returns a separate result. Review that output before using it in another application.

Keep going with related tools

All developer →