#33567: Builtin csrf_failure() view uses wrong charset
-------------------------+--------------------------------------
Reporter: MrVichr | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: 4.0
Severity: Normal | Resolution: needsinfo
Keywords: csrf | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------+--------------------------------------
Comment (by Claude Paroz):
When the charset is missing from a response, the browser has to guess
(either using a default, a user preference, or sniffing the content). We
should avoid that. Read https://www.w3.org/International/articles/http-
charset/index.en
--
Ticket URL: <https://code.djangoproject.com/ticket/33567#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f6af858fe-d5753e97-4303-4aef-b6b7-c6d9f1f5f0e4-000000%40eu-central-1.amazonses.com.
