Closed bsbudhwar closed 1 year ago
Hello @bsbudhwar ,
You didn't mention what version of ModSecurity you are using, but that configuration item is a newer one.
The error message that you have shared here would be expected if you are using a ModSecurity v3 version earlier than v3.0.6.
Hello @martinhsv,
I compiled libmodsecueity v3 (3.08) version and still giving the same error .
Then I don't know any scenario where what you have reported is possible. Also, given that this is not particularly new, and the item is in modsecurity.conf-recommended, it seems less likely that there is an actual bug here (I mean it would be surprising if there is an actual bug and no one else has encountered it after all this time).
Some things you could try:
SecAction "phase:2,id:1001,pass,log,msg:%{MODSEC_BUILD}"
If you're confident that everything is in order, you would probably need to share a complete and detailed set of steps that you used to build.
Closing, due to no further feedback.
[emerg] 1189764#1189764: "modsecurity_rules_file" directive Rules error. File: /etc/nginx/modsec/modsecurity.conf. Line: 58. Column: 34. Invalid input: SecRequestBodyJsonDepthLimit 512 in /etc/nginx/nginx.conf:43