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

Susan_Cahill_82's avatar
Susan_Cahill_82
Icon for Nimbostratus rankNimbostratus
Jul 20, 2006

Cookie Insert Persistance - Same V Server, different Service

I need to create an IRule that will do a cookie insert and I can't use other cookie persistant functions.     There are two different services set up (443 & 80) for the same virtual server, a us...
application delivery
dev
devops
iRules
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jul 21, 2006
Thanks for the clarification. I think this is your current configuration:

 

 

VIP:443 -> client SSL profile -> iRule1 -> pool1:80

 

VIP:80 -> iRule2 to redirect to VIP:443 (-> pool1:80??)

 

 

Are you redirecting all requests to VIP:80 to the VIP:443 using iRule2? Do requests ever make it to the nodes for the VIP:80?

 

 

If all requests to VIP:80 are being redirected to HTTPS or if no stateful content is being provided over HTTP, there shouldn't be any need to persist client requests to VIP:443 to the same node they used for VIP:80 (and therefore you shouldn't need to add a persistence profile to VIP:80).

 

 

Regardless, if you're using the same pool for both VIPs, the cookie insert persistence profile should work without setting the nodes in the pool to port 0. This assumes that the two VIP's are on the same IP address or host (so the client will actually send the cookie it received from VIP:80 to VIP:443).

 

 

This is a basic function of persistence. I don't think either rule should have any bearing on the peristence functionality. If this isn't working, I would suggest contacting support to get some assistance. It should be pretty straightforward for someone to take a look at your configuration in a tech.out and figure out exactly what's not working and why.

 

 

Aaron