Bug ID 455267: http explicit proxy route-domain parameter non-functional

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM, SWG(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2

Fixed In:
11.6.0, 11.5.1 HF3

Opened: Apr 02, 2014
Severity: 2-Critical
Related AskF5 Article:
K16430

Symptoms

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.

Impact

It is not possible to use the HTTP explicit proxy (or SWG) if the target of the connection is not in route-domain 0.

Conditions

When forwarding proxy requests to an IP address that results from a DNS resolution, the route-domain parameter is not used.

Workaround

This issue has no workaround at this time.

Fix Information

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.

Behavior Change