Re: [mod-security-users] mod-security-users Digest, Vol 6, Issue 22
Brought to you by:
victorhora,
zimmerletw
From: Ivan R. <iva...@gm...> - 2006-11-21 10:50:18
|
On 11/21/06, Dan Rossi <sp...@el...> wrote: > Hi, i was assuming this works as it is documented > > <Location /signup> > SecFilterInheritance Off > #SecFilterScanPOST On > > </Location> It is documented and it works. However, "SecFilterInheritance" prevents the rules from being inherited from the parent context but it does nothing to the configuration options. The configuration settings are always inherited. If you want something different to happen just provide different configuration. So, in your case you could do something like: <Location /signup> SecFilterInheritance Off SecFilterForceByteRange 0 255 </Location> > Are you saying for a particular location we have to set a completely > different set of rules to overwrite the default ones ? No. I am saying there are two different aspects that are inherited: rules and configuration. These are handled differently, as I explained above. > I cant manage to install mod sec 2 at all, any ideas how to compile this > into apache2 The instructions provided in the reference manual work for me. If you can be more specific about your troubles perhaps we can find out. Didn't Alberto just make the ModSecurity 2.x binaries for Debian available? -- Ivan Ristic |