iRules: Disabling Event Processing

The Problem One of our customers was recently trying to use LTM with iRules to replace their proxy servers. They wondered if, rather than building one big iRule that contained all the required logi...
Published Jun 10, 2008
Version 1.0
BIG-IP
news
tech tip
Skye_85590's avatar
Skye_85590
Icon for Nimbostratus rankNimbostratus
Jan 21, 2012
Originally posted by skbartl : "Using "event disable" only disables processing of the current iRule. If you have other iRules that are in subsequent order, they will be executed."

 

 

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!