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

Lightspeed_VT_5's avatar
Lightspeed_VT_5
Icon for Nimbostratus rankNimbostratus
Nov 16, 2007

HTTP 302 redirect

Our application requires session persistence. Because we have a lot of users sharing IP addresses (i.e. corporate clients), we've enabled OneConnect.     For reasons unknown, requests for exis...
application delivery
dev
devops
iRules
safeinst_110941's avatar
safeinst_110941
Icon for Cirrus rankCirrus
Mar 26, 2014

"Because we have a lot of users sharing IP addresses (i.e. corporate clients), we've enabled OneConnect."

 

I don't think OneConnect is what you want. OneConnect is tcp multicasting. It allows for multiple client tcp connections to utilize a single serverside tcp connection.

 

http://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html

 

If this is for HTTP traffic you more likely want to be using cookie persistence. So that different users with the same source IP will have unique persistence cookies.

 

http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-concepts-11-4-0/10.html

 

None of the above addresses the underlying issue. If your server is responding with a 302, you should look at why the server keeps doing this instead of attempting to put a band aide on the issue.