From: Ivan Ristic <ivanr@we...> - 2004-11-28 14:51:47
The SecFilterInheritance directive never affects the configuration data,
only rules. Maybe I should change its name to "SecFilterRuleInheritance"...
Small inconsistencies are a drawback of organic growth, I am afraid.
BTW, if you want to turn the filtering engine off, use "SecFilterEngine Off"
----- Original Message -----
Subject: RE: RE: [mod-security-users] [ANNOUNCE] mod_security 1.8.5 released
From: Mark <admin@...>
Date: 28-11-2004 14:40
> > -----Original Message-----
> > From: Ivan Ristic [mailto:ivanr@...]
> > Sent: zondag 28 november 2004 15:22
> > To: Mark; mod-security-users@...
> > Subject: Re: RE: [mod-security-users] [ANNOUNCE] mod_security
> > 1.8.5 released
> > It's the SecFilterForceByteRange directive. Set it to "1 255"
> > and the problem should go away.
> I will try that; thanks. I had:
> SecFilterForceByteRange 32 126
> > mod_security 1.8.x is more thorough than 1.7.x. That's why you
> > are getting the error. As for the audit log, didn't you turn
> > the audit log off with "SecAuditEngine Off"?
> Yes, I did:
> <Location /cgi-bin>
> SecFilterInheritance Off
> SecAuditEngine Off
> But my point was, that since I had turned off SecFilterInheritance for
> /cgi-bin/, and all its subdirs, I did not expect the SecFilterEngine to
> work in their to begin with.
> - Mark
> System Administrator Asarian-host.org
> "If you were supposed to understand it,
> we wouldn't call it code." - FedEx
Get latest updates about Open Source Projects, Conferences and News.