Bug ID 1959181: Proxy Select Agent does not persist clients to their selected upstream proxy

Last Modified: Jul 28, 2026

Affected Product(s):
BIG-IP APM, SSLO(all modules)

Fixed In:
17.5.1.8

Opened: May 23, 2025

Severity: 3-Major

Symptoms

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.

Impact

Each connection from the same client can be routed to a different upstream proxy.

Conditions

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.

Workaround

None.

Fix Information

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.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips