#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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):
* stage: Unreviewed => Accepted
Comment:
I don't think there is a use case for a `None` value. To deactivate
memory-based file uploads, I think that the official method is to remove
the `MemoryFileUploadHandler` from upload handlers.
In my opinion, the usage by `asgi.py` might be a bug. It should used
[https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-
DATA_UPLOAD_MAX_MEMORY_SIZE DATA_UPLOAD_MAX_MEMORY_SIZE], and mimic the
`MultiPartParser.parse()` code to raise `RequestDataTooBig` when it is
exceeded. To be confirmed…
--
Ticket URL: <https://code.djangoproject.com/ticket/30669#comment:1>
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.471d23244e4bb69593793caa49c57314%40djangoproject.com.
