Skip to content
littlekit.app

HTTP response inspector

Inspect pasted status lines, headers and bodies with sensitive response values redacted by default.

Begin with a status line, then Header: value lines, a blank line, and an optional body.
Authorization, cookies and API-key headers stay redacted unless you explicitly opt in.
Redacted response preview157 characters
HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8
X-Request-Id: req_demo_42
Set-Cookie: [redacted]

{"id":"note_42","title":"Morning notes"}
Processed on your device

How it works & useful details

Local-only workspace

This tool converts or inspects pasted text in your browser. It never sends a request, opens a URL, uploads a HAR, or stores your input.

Response format

Paste one HTTP status line followed by headers and an optional body after a blank line. This inspector parses pasted text; it does not retrieve a response from any server.

About this tool

HTTP response inspector breaks a pasted raw response into its status line, headers, and body so you can see the structure at a glance. It is designed for responses copied from a terminal, a proxy log, or a support thread.

The inspector works offline and applies redaction by default: sensitive header values and body snippets are masked unless you choose otherwise. That makes it practical to prepare a response for a public issue tracker.

How to use it

  1. Paste the complete raw response, starting with the HTTP status line.
  2. Review the parsed status, header table, and body preview.
  3. Toggle redaction only for fields you need to inspect closely.
  4. Copy the sanitized breakdown into your notes or ticket.

Worked example

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8
X-Request-Id: req_demo_42
Set-Cookie: session=example

{"id":"note_42","title":"Morning notes"}

is broken down into status 201, three headers with the Set-Cookie value redacted, and a 40-character JSON body. The blank line is what separates headers from the body, as in the HTTP message format itself.

Reading status codes

  • 2xx success: 200 OK, 201 Created (often with a Location header), 204 No Content.
  • 3xx redirection: 301 and 308 are permanent, 302 and 307 temporary, and 304 means the cached copy is still valid.
  • 4xx client errors: 400 malformed request, 401 missing or invalid credentials, 403 authenticated but not allowed, 404 not found, 409 conflict, 422 validation failed, 429 rate limited (check Retry-After).
  • 5xx server errors: 500 unexpected failure, 502 and 504 gateway or upstream problems, 503 temporarily unavailable.

Paste output from curl -i, a proxy log, or a test failure to see the parts clearly and share them with sensitive values removed. The inspector only parses the text you paste. It never contacts a server.

Frequently asked questions

Does it understand chunked or compressed bodies?

It splits text at the blank line and shows the body as pasted. Binary or compressed payloads should be decoded before pasting.

Why is a header value hidden?

Values that commonly carry secrets, such as cookies and authorization tokens, are masked by default to prevent accidental disclosure.

What is the limit?

Up to 100,000 characters per response.

Can I inspect an HTTP/2 response?

Yes, if it is written in the familiar text form with a status line. Tools like curl -i print HTTP/2 responses that way.