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

Update to reflect changes to SecRequestBodyInMemoryLimit for libModSecurity

Victor Hora
2017-08-22 17:23:45 -04:00
parent 255fa20b3b
commit 14a78b8520
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Reference-Manual.mediawiki

@@ -1228,14 +1228,16 @@ This directive is required if you want to inspect the data transported request b
'''Scope:''' Any '''Scope:''' Any
'''Version:''' 2.0.0 '''Version:''' 2.0.0-2.9.x
'''Supported on libModSecurity:''' Yes '''Supported on libModSecurity:''' No
'''Default:''' 131072 (128 KB) '''Default:''' 131072 (128 KB)
When a multipart/form-data request is being processed, once the in-memory limit is reached, the request body will start to be streamed into a temporary file on disk. When a multipart/form-data request is being processed, once the in-memory limit is reached, the request body will start to be streamed into a temporary file on disk.
; Note : libModSecurity is able to deal with request body in a file or in a buffer (chunked or not). Web servers have properties which controls whenever a request should be saved to a file or used as a buffer (e.g. client_body_buffer_size [https://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_buffer_size]) . If it is a file, ModSecurity will use the file to perform the inspection. If not, the buffer will be used.
== SecRequestBodyLimit == == SecRequestBodyLimit ==
'''Description:''' Configures the maximum request body size ModSecurity will accept for buffering. '''Description:''' Configures the maximum request body size ModSecurity will accept for buffering.