Forum Discussion

f5medmed_305667's avatar
f5medmed_305667
Icon for Nimbostratus rankNimbostratus
Jan 10, 2017

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?

 

application delivery
BIG-IP
devops

4 Replies

Sort By
  • Ryan_80361's avatar
    Ryan_80361
    Icon for Cirrostratus rankCirrostratus
    Jan 10, 2017

    What persistence method do you have configured on the virtual server?

     

    • f5medmed_305667's avatar
      f5medmed_305667
      Icon for Nimbostratus rankNimbostratus
      Jan 10, 2017

      The Default Persistence Profile is ssl and no fallback persistence profile.

       

      If I look up the properties for persistence ssl Name: ssl Partition: Common Persistence Type: SSL

       

      Then nothing is checked below that.

       

    • f5medmed_305667's avatar
      f5medmed_305667
      Icon for Nimbostratus rankNimbostratus
      Jan 10, 2017

      The Default Persistence Profile is ssl and no fallback persistence profile.

       

      If I look up the properties for persistence ssl Name: ssl Partition: Common Persistence Type: SSL

       

      Then nothing is checked below that.