#34709: charset should be ignored for the application/x-www-form-urlencoded
content
type.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
| Felisiak
Type: Bug | Status: assigned
Component: HTTP handling | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Replying to [comment:5 Mariusz Felisiak]:
> We could raise a warning when `self._encoding` is not `utf-8`, that it
will be ignored in Django 6.0. I'm just not sure it's worth doing.
The warning will probably only be ever raised on production servers, so
hardly visible in practice.
Did you explore what will happen in practice if an incoming request is
encoded in a different encoding and we try to decode it with `utf-8`?
Server error (500)? Bad request(400)?
--
Ticket URL: <https://code.djangoproject.com/ticket/34709#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018963625337-87cb06c5-cc67-4231-a8eb-e05e4a4dbbed-000000%40eu-central-1.amazonses.com.
