Bug ID 1064157: Http_proxy_opaque_get should constrain search to local/spawn flows, not looped flows

Last Modified: Feb 07, 2024

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

Known Affected Versions:
15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:

Opened: Nov 24, 2021

Severity: 3-Major


In a VIP-on-VIP (looped) situation, HTTP on one virtual server uses/reuses an existing 'http_proxy_opaque' whilst still in use by another virtual server that causes unexpected state changes in the opaque which may cause tmm to core.


Traffic disrupted while tmm restarts.


-- Explicit Forward Proxy SSL Orchestrator, in other words an L3 Explicit Proxy which is usually deployed in a VIP on VIP configuration -- Hostname resolution using explicit 'RESOLV::lookup' iRule in HTTP_PROXY_REQUEST on the explicit/client-facing VIP



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips