#18004: Django should not use `force_unicode(..., errors='replace')` when
parsing
POST data.
-------------------------------------+-------------------------------------
Reporter: mrmachine | Owner: aaugustin
Type: Bug | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: post data unicode | Triage Stage: Design
utf8 encode decode transaction | decision needed
aborted | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
All this ticket is based on the premise that browsers send "unencoded"
filenames -- ie. filenames as stored on disk, as a sequence of bytes.
If that's true, it's certainly documented somewhere. Can you look for some
documentation or specification of this behavior?
(This is hard for me to reproduce as I don't own any systems with a non-
utf-8 filesystem.)
--
Ticket URL: <https://code.djangoproject.com/ticket/18004#comment:11>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
