#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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"eea0bf7bd58cda4618ecc10133f0ad09effe1a2e" eea0bf7b]:
{{{
#!CommitTicketReference repository=""
revision="eea0bf7bd58cda4618ecc10133f0ad09effe1a2e"
Refs #30669 -- Removed incorrect branch in ASGIHander.read_body().
None is not valid for settings.FILE_UPLOAD_MAX_MEMORY_SIZE.
Always use SpooledTemporaryFile.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30669#comment:9>
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.3a7d4fd06abbe456e8369a3a3e842da2%40djangoproject.com.
