I am running ModSecurity 2 with SecRuleEngine DetectionOnly.
Even though it is set up for detection only, ModSecurity still acts as if
it is turned On in some instances (not all) and keeps some of my pages from
displaying properly(false positives).
What should I edit to keep from getting the following error which also keeps
one of my pages from displaying at all:
[Sun Mar 09 20:47:16 2008] [error] [client 192.168.0.1] ModSecurity: Output
filter: Response body too large (over limit of 524288, total length not
known). [hostname "www.mysite.com"] [uri "/someFolder/index.html"]
I tried adding a .htaccess file to the directory that contains this
particular page. For some reason, I get an internal server error or the
.htaccess file is ignored when trying to add something like the following to
a .htaccess file:
Use of .htaccess files is accepted on my server. The only time .htaccess
files do not work is when they contain code for ModSecurity. I have tried
using them in different directories for other ModSecurity issues and they
The only thing that works is editing the rules or adding something directly
to one of the Apache/ModSecurity config files.
So how can I "turn off" ModSecurity for individual pages or make sure this
particular page does not trigger this ModSecurity alert?