#9054: request.raw_post_data is empty for multipart/related posts
------------------------------------+---------------------------------------
          Reporter:  gruffudd       |         Owner:  nobody   
            Status:  new            |     Milestone:           
         Component:  HTTP handling  |       Version:  1.0      
        Resolution:                 |      Keywords:  multipart
             Stage:  Unreviewed     |     Has_patch:  1        
        Needs_docs:  0              |   Needs_tests:  0        
Needs_better_patch:  0              |  
------------------------------------+---------------------------------------
Comment (by chris chamberlin):

 The mod_python handler has this same bug.

 Another way this bug manifests itself: If I access the raw_post_data
 attribute first, the POST dict will be empty, even for multipart/form-
 data.  As it stands, you can get your data either in POST or
 raw_post_data, but not both.  Access to both is useful; I wrote middleware
 to mirror certain POST requests to another location, but it triggers this
 bug.

 My inexpert assessment is that this bug results from changing
 django.http.HttpRequest.parse_file_upload() to take a file-like object (so
 it can read chunks), instead of taking the entire request content from
 raw_post_data as it was done pre-1.0.

 An upload handler might help with a workaround?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9054#comment:2>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to