Does this tool send or replay the request?
No. The message is parsed as local data. DecodeLens does not connect to the Host header, request target, proxy, redirect, or any URL found in the body.
Raw HTTP Request & Response Inspector
Parse raw HTTP/1.x requests and responses, preserve ordered duplicate headers, inspect framing and multipart bodies, and create a separate redacted support copy without sending traffic.
Local input limit: 10 MB · Processing timeout: 12 s
How can I verify this?
Open your browser DevTools and the Network panel, optionally clear existing requests, then run the tool. Page assets or consent-based analytics may still load, but tool payloads, files, keys, and results are not sent for processing.
Inspect a raw HTTP message
Paste a complete HTTP/1.x request or response, or choose a local file. The parser reads octets in a disposable worker and never sends, replays, or fetches the message.
HTTP message analysis
The start line, ordered headers, framing diagnostics, inert body preview, multipart parts, nested artifacts, and redacted support copy will appear here.
HTTP message debugging without replay
DecodeLens parses the supplied HTTP/1.x octets locally, preserves header order and duplicates, applies explicit framing rules, and keeps every body or multipart preview inert.
Parsing, framing, and security boundaries
- No request, response, redirect, URL, cookie, proxy, or endpoint is sent, opened, or fetched.
- CRLF is canonical; bare LF can be inspected with an explicit finding. Malformed or ambiguous framing is reported rather than silently repaired.
- Chunked decoding and multipart parsing are bounded. HTTP multipart remains separate from the email MIME parser.
- The redacted copy is a separate diagnostic artifact and may not be replayable, especially when a body is binary or framing headers no longer describe the redacted representation.
- Parsing does not authenticate a sender, verify HTTP signatures, test credentials, or establish that a message is safe.
Related tools for this workflow
Continue with tools that decode, convert, inspect, or verify the same data.
- API & network
HAR File Analyzer & Sanitizer
Analyze HAR requests, failures, timing, transfer sizes, bodies, and sensitive fields; export a separate redacted copy.
Open tool - Developer Utilities
URL Parser & Builder
Inspect URL components and query parameters, edit them, and rebuild a valid URL.
Open tool - Data formats
JSON Formatter & Validator
Format, minify, validate, and explore JSON in a collapsible Object View without uploading data.
Open tool - Security & identity
JWT Decoder & Parser
Parse JWT segments and inspect formatted Header, Payload, and Signature data locally.
Open tool
Request and response examples
Inspect a copied request to review ordered headers, framing, JSON or form content, and exact nested artifacts. Response status lines and chunked bodies use the same bounded parser.
Raw HTTP
POST /v1/items HTTP/1.1\r\nHost: api.example.test\r\n…Parsed message
start line → ordered headers → framing → inert body → redacted copyRaw HTTP Inspector FAQ
Why are duplicate Content-Length headers highlighted?
Different recipients can interpret ambiguous framing differently. The inspector preserves every field line and reports the observed conflict; it does not claim exploitability.
Is the redacted copy safe to share or replay?
Review it before sharing. Detection is not proof that every sensitive value was found, and the diagnostic copy is not generated as a replayable request.