logo       

Re: mod-security-users Digest, Vol 6, Issue 22: msg#00105

apache.mod-security.user

Subject: Re: mod-security-users Digest, Vol 6, Issue 22

On 11/21/06, Dan Rossi <spam@xxxxxxxxxxxxxxxx> 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

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise