Persistence and the Cookie

Hello,

 

 

I assume you're talking about persistence for HTTP or (HTTPS traffic which the BIG-IP is decrypting with a client SSL profile). If that's the case, most commonly, administrators use cookie insert persistence.

 

 

The benefit to this is that it allows per-browser persistence. Contrast this with source address persistence where you are treating all clients coming from the same IP address as the same user in terms of persistence. So if you have a lot of clients connecting from the same IP address (through corporate or ISP proxies), cookie insert persistence is a simple way to distinguish between them. Just make sure to add a OneConnect profile to your VIP so that multiple HTTP requests over the same TCP connection are parsed individually for persistence (and load balancing).

 

 

I'm not sure what other docs are available on this. You might try searching further on AskF5, or see what other people suggest here.

 

 

Aaron