#18004: Django should not use `force_unicode(..., errors='replace')` when
parsing
POST data.
-------------------------------------+-------------------------------------
Reporter: mrmachine | Owner: aaugustin
Type: Bug | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: post data unicode | Triage Stage:
utf8 encode decode transaction | Unreviewed
aborted | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by mrmachine):
Thanks for the feedback. I will attempt to log the request body as you
suggested, and hopefully narrow down the cause of these errors.
However, while I understand the need to force incoming data to unicode
instead of carrying around who-knows-what-encoded bytestrings, I am still
not sure we should be doing so with `errors='replace'`, even if that turns
out to not be the cause of my particular problem. It seems like the
current code is itself a work-around to a problem we don't know exists
(and expect not to exist). A work-around that silently alters and corrupts
incoming data.
--
Ticket URL: <https://code.djangoproject.com/ticket/18004#comment:18>
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
