Add charset to JsonResponse

[Torsten Bronger]

Please change the default content-type of JSON responses from "application/json" to "application/json; charset=ascii" or "application/json; charset=utf-8". The way Django generates the JSON, it's guaranteed to work with both values of charset. HTTP itself doesn't define a default charset for application/* types AFAIK.

[Aymeric Augustin]

Can you clarify why this change is needed?

[Torsten Bronger]

Because I like don't like ambiguity, I overrode the content_type parameter in order to have a charset. But it would be nice if I needn't do this anymore in an upcoming Django version. It is a cosmetical problem I admit. The HTTP standard only states a default charset for text/* (namely 8859-1), so a client has to guess in case of application/* and in absence of charset, so I think it is good habit to make it explicit. Besides, there are no disadvantages, and it is a simple change.

[Tim Graham]

According to ​RFC 7159, "No "charset" parameter is defined for this registration. Adding one really has no effect on compliant recipients."

See also ​the same report in flask which was closed as invalid.

[Tom Christie]

Confirming tim's resolution. JSON responses in REST framework also don't include the charset, for the same reason.

[Serhiy]

What do you think about defaulting to UTF-8? Right now it's ASCII, AFAIU. While the RFC clearly recommends UTF. Should I bother opening new ticket for this?

[Tim Graham]

I believe it defaults to settings.DEFAULT_CHARSET which is 'utf-8' by default.