Cookie Persistence Failure Due To Client Behavior
Not being all that familiar with persistence behavior, we were thinking about two possible ways to resolve this:
1) Enable OneConnect. However we fear this will not address the situation where a second cookie overwrites the first in a case where a client has two outstanding HTTP transactions.
2) Enable source_addr as a Fallback persistence.
If we use source_addr as Fallback persistence though, won't that mean that the load-balancing decision happens during the intial handshake, and that the BigIP cookie becomes irrelevant?
Would appreciate some thoughts on how to get this working. Thanks.