#14035: Cannot access POST after request.encoding was set to a custom value
-------------------------------+-----------------------------------------
Reporter: Piotr Czachur | Owner: Piotr Czachur
Type: Bug | Status: assigned
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-----------------------------------------
Comment (by Silvan Spross):
hi all, I just found this ticket after I created a related question on
stackoverflow regarding the same sendgrid problem:
http://stackoverflow.com/questions/42862082/reencode-django-request-body-
with-another-encoding
is there a way to get around this at the moment? thank you for your help!
--
Ticket URL: <https://code.djangoproject.com/ticket/14035#comment:19>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.1fa914078f77ed886941eb47e3cff500%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
