f5medmed_305667
Jan 10, 2017Nimbostratus
F5 SSL Stickiness: tied to the name of the original URL?
Suppose you had a virtual server setup 10.10.200.21 reachable via SSL/443.
It has two resources serverA.foo.com and serverB.foo.com selected by round robin selection and reached at port 8080.
For a long time this works very well with users going to https://www.foo.com.
Then one day a developer decides to add a cname wow.foo.com which resolves to and he adds a link on the site with url wow.foo.com. When they click that link they sometimes have persistence problems.
My question is - if the session was initiated with would clicking wow.foo.com start a new SSL session that then pooches the stickiness?