You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 14, 2020. It is now read-only.
The following rule just propagates up a warning from the Apache log. This functionality does not work in other web servers (Nginx and IIS) and is not going to be supported in 3.x (see owasp-modsecurity/ModSecurity#1028). I think it makes some sense to remove this rule.
SecRule WEBSERVER_ERROR_LOG "@contains Invalid URI in request"
"msg:'Apache Error: Invalid URI in Request.',
severity:'WARNING',
id:920110,
...
The text was updated successfully, but these errors were encountered:
I would agree with @csanders-git. Having a rule that is just workable on a single environment is very confuse, specially because it is not clear that it is currently only available in Apache.
The following rule just propagates up a warning from the Apache log. This functionality does not work in other web servers (Nginx and IIS) and is not going to be supported in 3.x (see owasp-modsecurity/ModSecurity#1028). I think it makes some sense to remove this rule.
SecRule WEBSERVER_ERROR_LOG "@contains Invalid URI in request"
"msg:'Apache Error: Invalid URI in Request.',
severity:'WARNING',
id:920110,
...
The text was updated successfully, but these errors were encountered: