Loading...
Loading...
When per-request policy uses the Proxy Select Agent to route traffic to an upstream HTTP proxy pool, clients are not consistently sent to the same proxy on each new connection. A different proxy pool member may be selected each time even when a persistence profile is attached to the virtual server.
Each connection from the same client can be routed to a different upstream proxy.
This issue occurs when all of the following are true: -- LTM/APM virtual or SSLO topology uses a per-request policy with a Proxy Select Agent configured. -- A persistence profile is attached to the virtual server.
None.
The Proxy Select Agent now passes only the pool selection to the virtual server, which applies the configured persistence profile to select the correct member. This ensures clients are consistently routed to the same upstream proxy.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.