In previous version of ModSecurity when a rule fails the engine just stop processing rules in the same phase.
As we don't think it is a good idea the SecInterceptOnError were created. You can control if modsecurity will stop or continue processing rules.

On Tue, Apr 26, 2011 at 3:38 PM, Ivan Ristic <> wrote:
I can't figure out the purpose of SecInterceptOnError. From the name
it sounds as if ModSecurity will block when a rule fails, but all it
seem to do is stop processing further rules. (That's also what the
documentation says.) What's the intended use case? Why would I set
SecInterceptOnError to on?

Ivan Risti─ç

WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today.  Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
mod-security-users mailing list
ModSecurity Services from Trustwave's SpiderLabs: