How to disable iRule processing on keep-alive per request when using HTTP::respond

Hi RG,

 

 

Once you disable the HTTP_REQUEST event it will stay disabled on that TCP connection until it's re-enabled or the connection is closed. The only thing I can think of to allow you to bypass the logic of the other iRule(s) would be to set a local variable in the primary rule. The local variable is specific to that TCP connection so you don't have to worry about trampling with global variables between connections. The other rules can then check that local variable to see whether the code in the secondary rule(s) should be run.

 

 

Aaron