[FEATURE] Add modsecurity config/compatibility for SecRequestBodyNoFilesLimit

[thelittlefireman]

What's needed and why?

Hi, could it be possible to add a configuration for the SecRequestBodyNoFilesLimit in mod security ?

bunkerweb/src/common/core/modsecurity/confs/server-http/modsecurity-rules.conf.modsec

Line 28 in 9c602de

SecRequestBodyNoFilesLimit 131072

Current config

...
# maximum data size
SecRequestBodyLimit 52428800
SecRequestBodyNoFilesLimit 131072
...

Cause i've got some issue to get a specific app that upload more than 1 MB as raw body ("not a file")

Nov 28 23:45:39 172.16.1.1 85e7e5477190[26671]: 2024/11/28 23:45:39 [error] 17256#17256: *234903 [client  XX.XX.XX.XX] ModSecurity: Access denied with code 400 (phase 2). Matched "Operator `Eq' with parameter `0' against variable `REQBODY_ERROR' (Value: `1' ) [file "/etc/nginx/XXX.XXXX.XXX/server-http/modsecurity-rules.conf.modsec"] [line "23"] [id "200002"] [rev ""] [msg "Failed to parse request body."] [data "Request body excluding files is bigger than the maximum expected."] [severity "2"] [ver ""] [maturity "0"] [accuracy "0"] [hostname "XX.XX.XX.XX"] [uri "/picture"] [unique_id "173283393633.511094"] [ref "v0,1"], client: XX.XX.XX.XX, server: XXX.XXXX.XX, request: "POST /picture HTTP/1.1", host: "XXX.XXXX.XX"

Implementations ideas (optional)

Something similar to MAX_CLIENT_SIZE but like MAX_NO_FILES_CLIENT_SIZE

Code of Conduct

• I agree to follow this project's Code of Conduct