[f-nsp] Exactly what does 'sticky' base its stickiness on

[Chris Price]

Can 'sticky' L4 persistence be combined with HTTP 'cookie switching' to 
get distribution of load across http real servers? Ay negative affects 
of doing this? Any benefits? The F5 systems I have worked on provide 
this as one of the 'easy' persistence drop downs in the F5 web gui.

 From what you are saying below, if I enable SSL 'session-id', I should 
disable L4 'sticky' for a SSL real server - they should be treated as 
mutualy exclusive. Correct?


Mike Allen wrote:
> Sticky is source ip alone.  Turning on SSL session id or cookie 
> switching would use those instead, although the initial setup (with 
> sticky enabled) would use source ip prior to setting up a ssl session, 
> so I would turn off sticky for ssl if you are doing session switching, 
> otherwise you will see some funny load balancing.
>  
> Mike
>
> On Mon, Jun 2, 2008 at 10:30 AM, Chris Price <cprice at its.to 
> <mailto:cprice at its.to>> wrote:
>
>      I've been thru the SLB guide and cant find any info on exactly
>     what teh foundry bases its stickiness on.
>
>     Is it source ip alone, or source ip plus some sort of session id.
>     What about client cookies or jsessionid's?
>
>     If this is covered in a document, please point me at it and save
>     the typing space for all involved.
>
>     Cheers!
>
>     _______________________________________________
>     foundry-nsp mailing list
>     foundry-nsp at puck.nether.net <mailto:foundry-nsp at puck.nether.net>
>     http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>