#23949: Add charset to JsonResponse
-------------------------------------+-------------------------------------
Reporter: bronger | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.7
Component: HTTP handling | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/23949#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.96144f3049c7160f3951437e7d7bdbd7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
