Re: [mod-security-users] Modsec on Tiger?

[<li...@32...>]

on 2/13/06 1:57 PM, Ivan Ristic at iv...@we... wrote:

> li...@32... wrote:
>> 
>>>   Please do not tell us if it worked. BTW, the ModSecurity manual is
>>>   right here:
>>> 
>>>   http://www.modsecurity.org/documentation/modsecurity-apache/stable/
>> 
>> Ivan, Not sure why the attitude? If I did not need help figuring this out,
>> then I would not bother the list.
> 
>   Well, I'll explain, since I have to now.
> 
>   I was not giving you attitude, I was merely trying to give you a hint
>   that the collective time of the list members is wasted because,
>   IMHO, you don't want to spend some time reading the manual. I wrote the
>   manual *specifically* to avoid answering trivial questions. Not all aspects
>   of ModSecurity are easy, I'll give you that, but to write the
>   simplest possible rule *is* trivial.
> 
>   It's simply starting to get to me that out of all ModSecurity-related
>   questions I get (and there are a lot), answers to more than 90%
>   of them are already in the manual.
> 
>   Now, let's stop wasting everyone's time. Send us the debug log snippets so
>   that we can see if everything is working as expected.


No need, I fixed it but do not know why it broke.

Previously, I had...

SecFilterEngine DynamicOnly

And everything worked fine.

When I upgraded to Tiger, it no longer worked.

Changing it to ..

SecFilterEngine On

Made things start working again.

BTW, I am not a noob, I checked the manual first, but as you can now see,
this has nothing to do with 'not reading the manual'.

As a developer myself, I want to know if something is not working or not.
And yes I get frustrated with noobs myself, when they do not try to figure
something out for themselves first.