#33395: No error raised when FILE_UPLOAD_TEMP_DIR is not accessible
-------------------------------------+-------------------------------------
               Reporter:  Martin     |          Owner:  nobody
  Koščak                             |
                   Type:             |         Status:  new
  Uncategorized                      |
              Component:  File       |        Version:  3.2
  uploads/storage                    |       Keywords:  empty request large
               Severity:  Normal     |  file upload
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 This one took me a while to figure out, so I'm creating a ticket.
 The initial issue I had was, when I uploaded a larger file (+10MB), I
 received no data in request. The POST, GET and FILES attributes of request
 were all empty, only META attribute was OK.

 After a lot of digging I've found the root of my problem. I had invalid
 ownership set on FILE_UPLOAD_TEMP_DIR.
 Once the file exceeded FILE_UPLOAD_MAX_MEMORY_SIZE and was deemed as
 TemporaryUploadedFile, something happened, and I received an empty
 request.

 This could be solved much sooner, if an Exception was raised.
 This happened in production environment with Apache and WSGI.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33395>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.eb9bab5e4a7f087de006b8a50a852e2c%40djangoproject.com.

Reply via email to