iRules: Disabling Event Processing
Published Jun 10, 2008
Version 1.0Was this article helpful?
Thanks for sharing about "event disable all". A distinction should be made here considering iRules are driven by *events* and the handling of those events are contextual in nature. For example, if rule A acts on HTTP_REQUEST and then issues 'event disable' within that event context, rule B, which also acts on HTTP_REQUEST, will *NOT* act on HTTP_REQUEST unless it had something like "when HTTP_RESPONSE event HTTP_REQUEST enable" and an HTTP_RESPONSE came in. The quoted statement is not entirely false since subsequent rules acting on events other than HTTP_REQUEST would still execute. I just verified this is the behavior at least for base builds 10.2.1-10.2.3.
Cheers!