#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 |
------------------------------------+---------------------------------------
Comment (by zimnyx):
You say I shouldn't be doing that (modifying encoding of the HttpRequest),
while Django docs says:
===
HttpRequest.encoding
A string representing the current encoding used to decode form
submission data (or None, which means the DEFAULT_CHARSET setting is
used). You can write to this attribute to change the encoding used when
accessing the form data. Any subsequent attribute accesses (such as
reading from GET or POST) will use the new encoding value. Useful if you
know the form data is not in the DEFAULT_CHARSET encoding.
===
My case fits exactly in this scenario. So do we get each other ?
--
Ticket URL: <http://code.djangoproject.com/ticket/14035#comment:4>
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.
