Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4
Opened: Aug 12, 2015 Severity: 3-Major Related Article:
K93085358
The use of HTTP::proxy disable for proxy chaining might result in a mangled URL.
Mangled URL that the backend proxy rejects.
For each session, the very first request with the Proxy-Authorization header will get a RST, although the authentication is successful. That means that the request is not proxied to the backend proxy. Further requests are processed normally.
Use a modified iRule to work around this issue: when HTTP_PROXY_REQUEST { log local0. "[HTTP::method] [HTTP::uri]" if {[HTTP::header exists Proxy-Authorization]} { log local0. "Proxy-Authorization found" set loc [expr [string first [HTTP::host] [HTTP::uri]] + [string length [HTTP::host]]] set uri [string range [HTTP::uri] $loc [string length [HTTP::uri]]] HTTP::uri $uri log local0. "modified URI: [HTTP::uri]" unset loc unset uri } HTTP::proxy disable #pool /Common/P_proxy }
None