#21231: Limiting the number of variables and files that a POST request can
contain
-------------------------------+--------------------------------------
Reporter: epandurski@… | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by epandurski@…):
* status: closed => new
* resolution: wontfix =>
Comment:
Obviously, I have not been sufficiently clear in explaining the problem.
I agree that as you say "It isn't unusual to allocate 100MB or 200MB of
RAM per process in a Django application server", but it is not usual to
allocate 50MB of RAM *for processing a single request*. For example, you
may have 1 process (200MB) and 100 threads (say additional 100MB
combined), and that's OK, but when you get a blast of requests, continuing
malicious POST-data, each and every thread will have to create a huge
django request-object (100 X 50 = 5000MB combined).
Memory is a complex problem, and it might very well be the case that I did
not get it right. The last reply, though, doesn't appear to be predicated
on a very thorough understanding of the proposal.
--
Ticket URL: <https://code.djangoproject.com/ticket/21231#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/078.4d7ae89371a5b3b989b55e06ac3126c3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
