Forum Discussion

helenio's avatar
helenio
Icon for Nimbostratus rankNimbostratus
Apr 22, 2013

HTTP::disable keep cookie persistence

  Hello I'm using a iRule that disable HTTP profile when a particular URI is requested (this URL calls non http traffic using port 80 !!!).     With regular URIs I have persistence with...
application delivery
dev
devops
iRules
What_Lies_Bene1's avatar
What_Lies_Bene1
Icon for Cirrostratus rankCirrostratus
Apr 22, 2013
I think the persistence would be maintained for the actual HTTP traffic as long as it's flowing over different TCP connections. The issue is if the same connection within a session is used for the HTTP and non-HTTP traffic. Once the HTTP::disable command is used it will apply for the lifetime of that connection and HTTP::enable won't re-enable it as the CLIENT_ACCEPTED event is only fired once when a connection is first established. Move it to a HTTP event and that won't fire either as HTTP processing has been disabled. Catch 22 really.

 

 

However, you might be lucky and find a new connection is established just for the non-HTTP traffic - lets hope so.