#14035: Cannot access POST after request.encoding was set to a custom value
------------------------------------+---------------------------------------
Reporter: zimnyx | Owner: nobody
Status: closed | Milestone:
Component: HTTP handling | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: reopened => closed
* resolution: => wontfix
Comment:
You are taking the request object you are given, and you are changing it.
That is, you are *modifying* the request. You shouldn't be doing that.
Django receives a HTTP request and parses it. If the content type
specified in the HTTP request can be interpreted into multiple values,
Django will parse the raw content into a POST dictionary.
You have a use case where the content encoding isn't being transmitted as
part of the HTTP request. Therefore, it's up to you to parse the raw
request data.
--
Ticket URL: <http://code.djangoproject.com/ticket/14035#comment:3>
Django <http://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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
