Forum Discussion
iRule: Browser Error "The connection was reset"
I don't have OneConnect enabled here. What would that change?
What you're basically doing when you send traffic to different pools based on some request condition is something called "context switching". The problem is that load balancing decisions "stick" to the TCP session they're in. This becomes most apparent in a context switching environment when HTTP Keep-Alives are present. OneConnect allows you to load balance each request separately. Otherwise you may experience anomalous incorrect pooling.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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