github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2025-08-13 21:36:00 +03:00
Code Issues Packages Projects Releases Wiki Activity

Remove SecRequestBodyInMemoryLimit from configuration template

Browse Source 
It is no longer supported since 81879cd, so it would be better
to remove any mentions from configuration as well to avoid possible
confusions.
This commit is contained in:
Andrei Belov 2017-08-23 11:42:23 +03:00
parent 1d3c4c670d
commit f6af42c235
No known key found for this signature in database
GPG Key ID: 1465F6CF06C1F0CD
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
modsecurity.conf-recommended
View File

@ -38,12 +38,6 @@ SecRule REQUEST_HEADERS:Content-Type "application/json" \
SecRequestBodyLimit 13107200 SecRequestBodyLimit 13107200
SecRequestBodyNoFilesLimit 131072 SecRequestBodyNoFilesLimit 131072
# Store up to 128 KB of request body data in memory. When the multipart
# parser reachers this limit, it will start using your hard disk for
# storage. That is slow, but unavoidable.
#
SecRequestBodyInMemoryLimit 131072
# What do do if the request body size is above our configured limit. # What do do if the request body size is above our configured limit.
# Keep in mind that this setting will automatically be set to ProcessPartial # Keep in mind that this setting will automatically be set to ProcessPartial
# when SecRuleEngine is set to DetectionOnly mode in order to minimize # when SecRuleEngine is set to DetectionOnly mode in order to minimize