#5076: Request object should try to determine encoding
-------------------------------------+-------------------------------------
Reporter: dbr <daniel@…> | Owner: Claude
Type: | Paroz <claude@…>
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: fixed
Keywords: unicode conversion | Triage Stage: Ready for
charset POST request | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"3f3076edbf8d6fb204984a1a7fddbde408d5b104"]:
{{{
#!CommitTicketReference repository=""
revision="3f3076edbf8d6fb204984a1a7fddbde408d5b104"
[1.5.x] Fixed #5076 -- Properly decode POSTs with non-utf-8 payload
encoding
Thanks daniel at blogg.se for the report and Aymeric Augustin for
his assistance on the patch.
Backport of 6de6988f9 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/5076#comment:16>
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.
