#30669: Can FILE_UPLOAD_MAX_MEMORY_SIZE be set to None?
-------------------------------------+-------------------------------------
Reporter: Lincoln | Owner: nobody
Type: Bug | Status: new
Component: File | Version: master
uploads/storage |
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 Claude Paroz):
Replying to [comment:3 Carlton Gibson]:
> * Do we even need the `is None` branch, i.e. can't we just always used
the `SpooledTemporaryFile`?
+1, receiving in a `BytesIO()` without upper limiting looks like a simple
DOS attack vector.
I'm not sure about your explanation of later size check. What if a request
has "unlimited" (i.e. *very* big) length?
--
Ticket URL: <https://code.djangoproject.com/ticket/30669#comment:4>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.e3eaefb7fff5f35edfd16c6f34c2f623%40djangoproject.com.
