Bug ID 813673: The HTTP Explicit proxy does not work correctly with IPv6 clients connecting to IPv4 destinations over CONNECT

Last Modified: Oct 16, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 15.0.0, 15.0.1

Opened: Aug 09, 2019
Severity: 3-Major

Symptoms

A typical configuration of the HTTP Explicit Proxy includes four virtual servers: -- Two virtual servers for the Explicit Proxy, one IPv4, one IPv6. -- Two general-purpose virtual servers: one IPv4, one IPv6. The general-purpose virtual servers allow handling of CONNECT tunneling over the HTTP-tunnel interface. Unfortunately, if an IPv6 client tries to CONNECT to an IPv4 destination, it fails, returning a 503 status error. This is due to the IPv6 general-purpose virtual server not being found when performing the destination lookup.

Impact

The client will not be able to CONNECT through the explicit proxy to an IPv4 address.

Conditions

-- The HTTP explicit proxy is used on an IPv6 address. -- 'default-connect-handling deny' is configured on the explicit proxy HTTP profile. -- IPv4 and IPv6 general-purpose virtual servers exist on the HTTP-tunnel interface. -- The client connects, and uses CONNECT to proxy to an IPv4 address.

Workaround

None.

Fix Information

None

Behavior Change