Network
Content-Type Inspector
Check how a declared Content-Type is structured before debugging a body parser.
How this tool works
Media type and parameters influence payload interpretation. A quoted multipart boundary and an explicit charset are common places for mismatches.
A syntactically valid header does not prove that payload bytes match the declared media type or character encoding.
Examples
- Read application/problem+json.
- Extract a quoted multipart boundary.
- Inspect charset on text content.
Common use cases
Check a multipart boundary or charset mismatch.
Worked synthetic example
Valid example
Content-Type: text/plain; charset=utf-8
Expected: Type text/plain and charset utf-8. The declaration describes intended interpretation, not actual bytes.
Failure or warning to recognize
Warning / interpretation
Content-Type: application/json while the response contains CSV bytes.
Expected: Malformed media-type syntax reports an error; a valid application/json declaration cannot prove its body is JSON.
Related guides
Official references
Related tools
HTTP Response InspectorInspect status, headers, cookies, content type, cache and CORS fields in a response.HTTP Header AnalyzerParse a raw header block and redact a documented set of common credential-bearing fields.XML Formatter and ValidatorValidate XML syntax and format element-only structures locally.