#30669: Can FILE_UPLOAD_MAX_MEMORY_SIZE be set to None?
-------------------------------------+-------------------------------------
Reporter: Lincoln | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
FILE_UPLOAD_MAX_MEMORY_SIZE, |
None, settings |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
> As it stands if the request is "unlimited" we'd end up using a lot™ of
disk space.
But this applies equally to the existing WSGI code right? Django doesn't
have a limit on the total file data that can be uploaded. (Does it? — I've
always set a sensible value at the nginx level...)
The only difference here is we have this extra buffer layer. (So we read
the bytes, presumably to disk, twice, for the length of the request.)
--
Ticket URL: <https://code.djangoproject.com/ticket/30669#comment:7>
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/070.aec7fdbd5364d2bc04916bbc9a2d6fad%40djangoproject.com.
