Bug ID 932937: HTTP Explicit Proxy configurations can result in connections hanging until idle timeout.

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 16.0.0,

Fixed In:
16.1.0, 16.0.1, 15.1.1,

Opened: Jul 31, 2020

Severity: 4-Minor


After an HTTP return code of 400 Bad Request or 403 Forbidden, connection table entries may not be removed from the connection table until they reach the idle timeout threshold.


The hanging connection table entries can cause subsequent connections from the same source port to fail. Also, the subsequent connection attempts can cause the idle timer to be reset.


-- HTTP Explicit Proxy Configuration. -- BIG-IP HTTP response contains a 400 Bad Request or 403 Forbidden status code.


Use an iRule to prevent connections from hanging: when HTTP_REJECT { after 1 }

Fix Information

HTTP Explicit Proxy configurations no longer results in connections hanging until idle timeout.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips