Forum Discussion
Problem with session persistence using CARP when load balancing a McAfee Web Gateway cluster using progress page for downloads
If your HTTP Proxies are explicit (not transparent), same connection can carry multiple HTTP requests and not wait for their respective answer (HTTP 1.1 and pipelining). In that case, without OneConnect, when CARP will select another pool member, the BigIP will disconnect the pool member handling the existing connection, and connect to the new pool member. With oneConnect, the new pool member will receive a new connection, and the existing connection with the "1st" pool member will be kept.
I haven't checked since version 10 if the behavior remains the same.
HTH
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com