For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Joel_Newton's avatar
Joel_Newton
Icon for Cirrus rankCirrus
Oct 18, 2016

iRule still executing for current browser session after being removed from virtual server

We're experiencing this behavior for a maintenance iRule that is frequently added to and removed from virtual servers. This primarily seems to occur when the same browser session is used. Starting a new browser session after the iRule has been removed doesn't cause the iRule to execute. Would something be getting cached, or some keep-alive property be causing this behavior? Is it expected?

 

Thanks.

 

v 11.6.0 HF4

 

application delivery
iRules
LTM

1 Reply

  • Walter_Kacynski's avatar
    Walter_Kacynski
    Icon for Cirrostratus rankCirrostratus
    Oct 18, 2016

    This is the behavior of iRule design as they are cached per TCP flow. This is why starting a new browser session "works" by creating a new TCP socket. To force this to clear out, you could use an 

    HTTP::respond Connection close
    in your iRule to create a new socket for every request. Depending on your traffic volume this could cause additional load due to the increased overhead of generating new socket connections.