Josh,
> Editing the CRS rules directly is not recommended as it makes upgrading > the rules much harder. Furthermore, its probably a good idea to upgrade > ModSecurity to the latest version as there was recently a DoS related > vulnerability patched. Once you are running a more recent version, your > options for handling false positives becomes significantly more flexible as > well, see: > > http://blog.spiderlabs.com/2011/08/modsecurity-advanced-topic-of-the-week-exception-handling.html > > I know that using the latest version is better, but I have some practical difficulties to upgrade at the moment. Will do that only after 6 months. > On ModSec 2.5.12, you can simply white-list the offending rule/s by > including something like the following *before* you include the offending > CRS rules. > > <Location /iredadmin/login> > SecRuleRemoveById 960010 > </Location> > > This solution is fine for me. I gave this in apache.conf as follows. But it is not working (still forbidden). Is it Location or LocationMatch ? Thanks. <IfModule security2_module> <Location /iredadmin/login/> SecRuleRemoveById 960010 </Location> Include modsecurity_crs/modsecurity_crs_10_setup.conf Include modsecurity_crs/activated_rules/*.conf </IfModule>
_______________________________________________ Owasp-modsecurity-core-rule-set mailing list Owasp-modsecurity-core-rule-set@lists.owasp.org https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set
