#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: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by epandurski@…):
> Isn't that covered by Apache's LimitRequestBody already?
I almost have forgotten what were my intentions with the
"FORM_DATA_MAX_FIELDS_TOTAL_LENGTH" field :)
I believe they are almost the same, except for 2 things:
1) LimitRequestBody's context is "server config".
"FORM_DATA_MAX_FIELDS_TOTAL_LENGTH" is specific to the web-application.
There might be many different applications running on one server, doing
different CPU/memory intensive stuff.
2) FORM_DATA_MAX_FIELDS_TOTAL_LENGTH is only about "application/x-www-
form-urlencoded" and "multipart/form-data" MIME types, which I believe are
the only MIME types which content django may decide to load into memory
(is that correct?). Notice that somebody may want to allow POST-ing other
MIME-types of big data, and yet have his/her django web-application
protected from DoS attacks.
--
Ticket URL: <https://code.djangoproject.com/ticket/21231#comment:20>
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.71aa9390c92b6fa5194b947d540786a6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
