Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unfiltered.response.JsonContent allows charset param which is wrong #372

Open
hamnis opened this issue Feb 20, 2017 · 0 comments
Open

unfiltered.response.JsonContent allows charset param which is wrong #372

hamnis opened this issue Feb 20, 2017 · 0 comments

Comments

@hamnis
Copy link
Contributor

hamnis commented Feb 20, 2017

From RFC-7159:

https://tools.ietf.org/html/rfc7159#section-8

JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default
encoding is UTF-8, and JSON texts that are encoded in UTF-8 are
interoperable in the sense that they will be read successfully by the
maximum number of implementations; there are many implementations
that cannot successfully read texts in other encodings (such as
UTF-16 and UTF-32).

https://tools.ietf.org/html/rfc7159#section-11

The MIME media type for JSON text is application/json.

Type name: application

Subtype name: json

Required parameters: n/a

Optional parameters: n/a

No parameters are allowed, meaning that specifying charset should not be possible.

@hamnis hamnis changed the title unfiltered.response.JsonContent allows charset param which is wrong unfiltered.response.JsonContent allows charset param which is wrong Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant