#19101: Non ascii chars in form cause Internal Server Error
-------------------------------------+-------------------------------------
Reporter: kristall | Owner: aaugustin
Type: Bug | Status: new
Component: Forms | Version: master
Severity: Release blocker | Resolution:
Keywords: encoding | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
Now that we know for sure that the content of the request is `x-www-form-
urlencoded`, it should be encoded and composed of only ASCII chars at this
point, AFAIK, so decoding it with 'utf-8' or 'ascii' or even any encoding
should not make any difference. The charset specified in the request is
then used later in `QueryDict` initialization to decode (in the sense of
url decoding) the query string content.
--
Ticket URL: <https://code.djangoproject.com/ticket/19101#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
