-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecRequestBodyLimit does not get properly merged from upper contexts #142
Comments
…y#142 While here, adjusted request body tests for flawless parallel execution.
The proposed PR does not fix configurations like the following though:
I.e. in the above configuration location block will still use SecRequestBodyLimit from http level (128) instead of locally redefined (512). |
Using something like this in
I'm happy to extend the PR (+ tests) if this is considered as desired behavior. |
OOP-friendly approach (incomplete, just an example:
|
While here, adjusted request body tests for flawless parallel execution.
See the following for details: #142 owasp-modsecurity/ModSecurity#1978 #143 owasp-modsecurity/ModSecurity#1990
…y#142 While here, adjusted request body tests for flawless parallel execution.
Reproducible with the following test:
Moving rules under the location context makes it work.
Currently investigating this one by digging in the
mergeProperties()
thing here:https://github.com/SpiderLabs/ModSecurity/blob/v3/master/headers/modsecurity/rules_properties.h#L311
The text was updated successfully, but these errors were encountered: