Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP LTM, SWG
Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10
Fixed In:
11.6.0
Opened: Apr 02, 2014 Severity: 2-Critical Related Article:
K16430
The http profile (with proxy-type explicit) lets you specify a route-domain to use for forwarding http (proxy) requests. This route-domain parameter is not always used.
It is not possible to use the HTTP explicit proxy (or SWG) if the target of the connection is not in route-domain 0.
When forwarding proxy requests to an IP address that results from a DNS resolution, the route-domain parameter is not used.
This issue has no workaround at this time.
When forwarding proxy requests to an IP address that results from a DNS resolution, the route-domain parameter is now used correctly and it now is possible to use the HTTP explicit proxy (or SWG) when the target of the connection is not in route-domain 0.