From f6af42c235567e2f7e40600c7d886b1bba91d9f9 Mon Sep 17 00:00:00 2001 From: Andrei Belov Date: Wed, 23 Aug 2017 11:42:23 +0300 Subject: [PATCH] Remove SecRequestBodyInMemoryLimit from configuration template It is no longer supported since 81879cd, so it would be better to remove any mentions from configuration as well to avoid possible confusions. --- modsecurity.conf-recommended | 6 ------ 1 file changed, 6 deletions(-) diff --git a/modsecurity.conf-recommended b/modsecurity.conf-recommended index 728afc1a..8ad9b102 100644 --- a/modsecurity.conf-recommended +++ b/modsecurity.conf-recommended @@ -38,12 +38,6 @@ SecRule REQUEST_HEADERS:Content-Type "application/json" \ SecRequestBodyLimit 13107200 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. # Keep in mind that this setting will automatically be set to ProcessPartial # when SecRuleEngine is set to DetectionOnly mode in order to minimize