#10902: FileUploadHandler not working, requests are always buffered.
--------------------------------------------------+-------------------------
 Reporter:  tkopc...@gmail.com                    |       Owner:  nobody    
   Status:  new                                   |   Milestone:  1.0.3     
Component:  File uploads/storage                  |     Version:  1.0       
 Keywords:  fileuploadhandler buffering requests  |       Stage:  Unreviewed
Has_patch:  0                                     |  
--------------------------------------------------+-------------------------
 I've got a problem with limiting the maximum size of a file uploaded
 to my webapp. I subclassed FileUploadHandler and everything is working
 fine, but only with Django development server.

 When running on lighttpd or nginx with mod_fastcgi (actually it
 behaves the same with apache + mod_python) my 'new_file' and
 'receive_data_chunk' methods are called *after* whole request has been
 uploaded to the server... And my intention is to raise SkipFile/
 StopUpload when uploaded data exceeds 100 kB or it's not an image.

 I thought it's a problem with the web servers, but since not one of them
 is actually working, it leads me to believe that it might be a problem
 with Django.

 System: Ubuntu Linux 9.04, lighttpd-1.4.19, Django 1.0.2.

 Steps to reproduce: attempt to upload an image file larger than 1 MB using
 attached upload handler.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10902>
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-updates@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to