951718 - Manifest validator suddenly doesn't like `charset=utf-8`

Status: RESOLVED FIXED

(Marketplace Graveyard :: Validation, defect)

Description

[Felix E. Klee]

Today I got an automated email that the manifest of my app [ROTOGAMEsq][1]
is not valid anymore. So I checked with the [validator][2]:

> **Your app failed validation with 1 error.**
>
>   * Your manifest file was not encoded as valid UTF-8.

I eventually found out that the validator doesn't like `Content-Type`:

    application/x-web-app-manifest+json; charset=utf-8

After I removed `; charset=utf-8`, the validator accepted the manifest.

In the past the above content type was no problem. Documentation [mentions][3]
that the encoding may explicitly be specified (although superfluous for UTF-8):

> The manifest must be in UTF-8 encoding in order for the app to be submitted
> to Firefox Marketplace. It is recommended that you omit the byte order mark
> (BOM). Other encodings can be specified with a charset parameter on the
> Content-Type header (i.e. Content-Type: application/x-web-app-manifest+json;
> charset=ISO-8859-4), although this will not be respected by the Marketplace.

[1]: https://marketplace.firefox.com/app/rotogamesq
[2]: https://marketplace.firefox.com/developers/validator
[3]: https://developer.mozilla.org/en-US/Apps/Developing/Manifest

Comment 1

[Wil Clouser [:clouserw]]

Thanks for filing.  Cvan fixed this over in https://bugzilla.mozilla.org/show_bug.cgi?id=941480#c15 and the fix is already live on the site.