Content-Type troubleshooting

Content-Type charset errors

A charset belongs after the media type as a parameter, separated with a semicolon. Incorrect separators, missing values, malformed quotes, and duplicate declarations can make a Content-Type value invalid or ambiguous.

Check the complete value

A typical value has this shape:

text/html; charset=utf-8

Paste your value into CorrectMIME to check its syntax and see a canonical form. The validator checks the string; it does not fetch a URL or inspect a file.

Validate a Content-Type value

Common charset syntax problems

Missing semicolon: application/json charset=utf-8
Missing value: text/plain; charset=
Malformed quotes: a quoted value must have a matching closing quote.
Duplicate charset parameters: repeated parameter names are ambiguous and should be resolved.
Unexpected separators or whitespace: parameter syntax still requires a name, equals sign, and value.

Syntax is not encoding detection

A well-formed charset declaration does not prove that the bytes were actually encoded with that character set. CorrectMIME validates the Content-Type value only; it does not inspect or decode the associated content.