Forum Discussion

Nimbostratus

Dec 15, 2015

iRule error after upgrade version (Operation not supported. Multiple redirect/respond invocations not allowed)

Hi, good afternoon. After upgrade a BIG IP OS from 10.2.4 to 11.5.1 HF10, I started to see a lot of errors in LTM log. I have many iRules in my system and many of those iRules are givin me "Operati...

Nimbostratus

Dec 15, 2015

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
MVP
Dec 15, 2015
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
Hannes_Rapp
Nimbostratus
Dec 15, 2015
Indeed, but if needed, you can also add a 'TCP::close' function after the 'event disable' function, to eliminate any possibility of problems with long sessions. A new TCP handshake (and possible SSL handshake) after each F5-initiated HTTP response or redirect should not be a performance hazard. You can achieve the same by appending a 'Connection Close' flag with your HTTP::respond functions. Yet another possibility is conditionally re-enabling the HTTP_REQUEST event, but i'd just prefer closing down on the TCP level for simplicity.
Kai_Wilke
MVP
Dec 15, 2015
Hi Hannes, thanks for confirming. So nothing has changed since then... :-( BTW: Did you already tried to use LTM Policies to reenable events on every single request? Could be an option now, or isn't it? Cheers, Kai
Kai_Wilke
MVP
Dec 16, 2015
Hi Hannes, just tried LTM Policies with expression [event enable all] on each request. Works like a charm... ;-) Cheers, Kai