Report

Help us improve this tool

HTTP Message Parser

Split raw HTTP messages into method, path, status, headers, and body in the browser.

O M T

Split raw HTTP requests and responses

Debugging proxies, load balancers, and integration tests often leaves you staring at a single text blob: request line, headers, blank line, then body. This parser recognizes both outbound requests (METHOD /path HTTP/1.1) and inbound responses (HTTP/1.1 200 OK), lists headers in order, and isolates the message body for inspection or copy/paste.

Typical workflows

  1. Paste a captured request from Charles, mitmproxy, or curl -v output (headers only).
  2. Confirm Host, Content-Type, and auth headers before replaying the call.
  3. Parse error responses to read JSON or XML bodies without manual splitting.

Build Authorization headers for replay tests with the Bearer Auth Header Builder.

Frequently Asked Questions

Does this send traffic to my URL?

No. Parsing is offline in the browser; nothing is executed on the network.

Which HTTP versions are supported?

Start lines using HTTP/1.0 or HTTP/1.1 notation are accepted. HTTP/2 binary frames are not supported.

How are folded headers handled?

Obsolete header folding (lines starting with whitespace) is not unfolded; paste already-normalized captures for best results.