Hi Ivan,

I always check to see if a ModSec configuration file is being loaded by purposely inserting bad syntax in the *.conf file, then restarting Apache. If Apache is picking up the conf file, Apache will not start and give you the line number of the syntax error plus the file name.


On Wed, Jan 28, 2009 at 12:42 PM, Ivan Rodriguez <ivanoch@gmail.com> wrote:
Hi People I'm trying to configure mod_security2, in order to stop cross scripting attacks
for an application server running Weblogic, I've compiled the module put the configuration in place
inside of the virtual host I've enabled SecRuleInheritance On, I've load all the rules inside of the package
set the the Maximum Debug Level, and I can't see that the mod_security is working
any suggestion ? any easy way to test it ?


This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
mod-security-users mailing list
Commercial ModSecurity Appliances, Rule Sets and Support: