1266023 - JSON's default charset should be UTF-8

Status: RESOLVED DUPLICATE of bug 741776

(Core :: DOM: Core & HTML, defect, P3)

Description

[amitavmohanty01]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36

Steps to reproduce:

I have a REST api that returns JSON with header "Content-Type: application/json". According to https://tools.ietf.org/html/rfc7159 the default encoding of JSON is Unicode. However, FF initially showed the response in Western encoding. I suspect that default encoding is picked based on the default of HTTP 1.1.



Expected results:

For all responses that have json as the content type, the default encoding should be UTF-8.

Comment 1

[stewartrand]

I have experienced the same issue, with application/json content encoded with UTF-8 being interpreted as being "windows-1252" encoding.

The server-side workaround is to get the web server to provide "Content-Type: application/json; charset=utf-8" in its responses instead of "Content-Type: application/json". Firefox then interprets the encoding as UTF-8.

Comment 2

[Alex Vincent [:WeirdAl]]

I'm not entirely opposed to this, but if this happens (particularly in JSON.stringify), I need to know about it.

Comment 3

[u408661]

I don't think necko does anything with character encodings for JSON other than passing any info it has to the consumer.

Comment 4

[amitavmohanty01]

Its rather ld to revive but do we have a consensus?

Comment 5

[amitavmohanty01]

(In reply to amitavmohanty01 from comment #4)
> Its rather ld to revive but do we have a consensus?

*late

Comment 6

[Masatoshi Kimura [:emk]]

Is this still an issue? Firefox 53+ will always treat application/json resources as UTF-8 when they are loaded as documents.
For XHR, Firefox will default to UTF-8 from the start. For fetch, Firefox will always treat them as UTF-8 from the start.