Forum Discussion
Hannes_Rapp
Nimbostratus
Assuming all your iRules are the same as your sample, replace
return
with event disable
function in all iRules that invoke redirects or responses. The return function is not needed here. The event disable function should be called after each redirect or response statement, unless you merge the iRules together so that this particular TCL error can no longer occur. By doing so, you may also want to look into iRule execution priorities to make sure no important functionality is superseded.
https://devcentral.f5.com/questions/stop-processing-irule-s-if-condition-is-met
Kai_Wilke
Dec 15, 2015MVP
Hey Hannes,
as far as I know "event disable" is persistent to the TCP connection. So it would cause keep-alive'ed connections to not trigger the HTTP_REQUEST events on the very next request. Isn't it?
Cheers, Kai