-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Problem of "Rule action" at Phase H #1592
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
Comments
And when set SecAuditEngine On ,All requests seem to have been warned at Phase H. But that's not the case. |
Hi @nobodysz, What is your SecDefaultAction status for this phase? Notice that this specific rule may not got the request blocked, instead it may increased the anomaly_score. |
Hi @zimmerle ,
|
As of 39fb75c this issue is partially solved. Notice that the error code is not yet filled. Working on it ... |
@zimmerle thank you about your reply. |
As of 34e8b14 the behavior is the same [or very close] as ModSec 2.x on Apache. |
@zimmerle Thanks for fix it. I upgraded my version and it's normal. |
Hi ~
I have compiled libmodsecurity v3, when requests were blocked with
SecRuleEngine On
.The rule action is "Warning". but I guess it should be "Access denied with code"?
Reference resources in waf-fle:
The text was updated successfully, but these errors were encountered: