Stop event processing for multiple rules

Thanks Deb and hoolio for your replies.

 

 

I had pretty much already decided that one rule was better than two. The need to have inter-dependence with flags etc. defeats the purpose of splitting the rules. It was a naive attempt at writing modular rules, but without user defined functions or subroutines that's not really practical.

 

 

unRuleY, would I need to worry about race conditions, such as when a second request is received on a connection before a response is received to a prior request which had disabled the HTTP_REQUEST event?