About The HTTP Request Parser

The HTTP Request Parser converts a raw request line, headers, and optional body into structured JSON for debugging API clients, proxies, webhooks, and captured traffic.

The parser runs locally in your browser and preserves the request body as text. Sanitize authorization headers, cookies, tokens, and customer payloads before pasting production data.

How to Parse an HTTP Request Online

1. Paste the raw request into the Raw HTTP request box, starting with the method line.
2. Keep the blank line between headers and body when a body is present.
3. Click Parse Request to build the JSON summary.
4. Copy the parsed method, target, version, headers, and body for debugging or documentation.

Choosing Options Correctly

Request line:
- Use the original line, such as POST /api/login HTTP/1.1.
- If parsing fails, check that method, target, and HTTP version are all present.

Headers and body:
- Keep one header per line with a colon after the header name.
- Leave one empty line before the body so the parser can split the sections cleanly.

Common Use Cases

• Inspecting copied cURL or proxy request captures.
• Documenting request payloads while debugging API integrations.
• Checking whether required headers are present before replaying a request.
• Teaching HTTP message structure with a visible JSON result.

Quick FAQ

Does it send the request?
No. It parses raw HTTP request text and does not connect to the target server.

Can it parse a body?
Yes for simple raw bodies, but it will not fully interpret every multipart, compressed, or binary body.

Why did I get an invalid request line error?
The first line should look like METHOD path HTTP/version. Missing method, path, or version can fail parsing.

Should I paste real Authorization headers?
Avoid live tokens, cookies, or API keys. Redact sensitive headers before parsing.