Network
HTTP Response Inspector
Paste a response snippet to separate its status line, fields, and body preview.
How this tool works
Response metadata explains how clients interpret a body, cache it, expose it across origins, and handle cookies. The report retains duplicate header lines for inspection.
A pasted response lacks request context and browser policy state. Use the dedicated CORS and header tools for deeper field-specific analysis.
Examples
- Review a 415 response media type.
- Inspect Cache-Control and ETag.
- Find Set-Cookie fields without exposing values.
Common use cases
Worked synthetic example
Valid example
HTTP/1.1 415 Unsupported Media Type Content-Type: application/problem+json
Expected: Status 415 and problem+json media type. The fields suggest a media-type mismatch to investigate with the request.
Failure or warning to recognize
Warning / interpretation
HTTP/1.1 200 OK with Content-Type: application/json but a non-JSON body.
Expected: A malformed status line or header reports a parse error; a valid Content-Type is not body validation.