Moderator: Phil Barton
It is my understanding that the SPS Client requires any load balancer which sits between the client and an SPS server farm to allow for session stickiness/affinity.
Our F5 vendor is suggesting that we use their cookie feature to do this. That is, new sessions are issued new cookies, and thus traffic can be appropriately routed based on the presence of the returned cookie in subsequent requests.
So my question is: The SPS client uses the http protocol to communicate to the SPS servers, but will it respect the load balancer's request that an issued session cookie be stored on the client and returned with all further traffic coming from that SPS session ?
Upon the load balancer seeing the first unique CID value, it should pick a server to route to and remember the answer. If the load balancer doesn't see the CID value for more than 15 mins, it should be safe for the load balancer to drop the cache entry.
Sr. Software Architect
You previously mentioned:
Does this also hold true for custom applications which are built using the SDK ?The SPS application sends an url query params hint called "cid". This value is mantained by the SPS app.
If not, how can these types of applications manage the desired cid for their session?