connection pooling proxies & cookie persistence

Hi James.. I solved, it but not with an iRule. Here was the Tech Support response that helped me solve this issue.

 

 

Hi Josh,

 

 

You are correct in that BIGIP is not looking for cookies in connections once the session is established. This is by design, the idea being that once a session is established, there is no longer a need to make a loadbalancing decision (ie, look for a cookie).

 

 

However, with the OneConnect profile, we should be able to get BIGIP to inspect every header. I would like you to try the following:

 

 

--create a custom OneConnect profile based on the stock OneConnect profile

 

--adjust the source mask to 255.255.255.255

 

--apply this new OneConnect profile to your virtual and retest.

 

 

This should force BIGIP to inspect for cookies.

 

 

Here is some information on OneConnect for you:

 

 

http://tech.f5.com/home/bigip-next/manuals/bigip9_2_2/bigip9_2_2config/BIG-IP_9_2_2ltm_guide-06-1.htmlwp1187154

 

Let me know how it goes.

 

 

Thanks!

 

 

Lynn Curtis

 

F5 Networks Support | www.f5.com

 

International: +800-11275435 | USA: 1-888-882-7535