#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
While starting to review the patch, and looking for more recent
considerations than the old 1866 RFC, I read
https://url.spec.whatwg.org/#application/x-www-form-urlencoded which is
worth a read. Quoting a note:
`A legacy server-oriented implementation might have to support encodings
other than UTF-8 as well as have special logic for tuples of which the
name is ``_charset``. Such logic is not described here as only UTF-8 is
conforming.`
I don't necessarily re-question our previous discussions/decisions,
however we might be prepared to receive some complaints as it may be that
non-conforming agents start to produce BadRequest errors. Difficult to say
before going to production!
--
Ticket URL: <https://code.djangoproject.com/ticket/34709#comment:15>
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/0107018a226deaec-e0d46ff0-f2ab-4880-950d-31e069046cff-000000%40eu-central-1.amazonses.com.
