Bug ID 1498361: Custom HTTP::respond does not fire as part of custom connect-error-message in HTTP explicit proxy profile.

Last Modified: Jun 22, 2024

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3

Opened: Feb 01, 2024

Severity: 3-Major

Symptoms

HTTP::respond does not fire when custom error message is configured in http explicit proxy config.

Impact

The custom error message configured in the explicit proxy config is not relayed back to client and the actual response from backend server is repeated.

Conditions

1. In http explicit proxy config, configure custom error message using 'HTTP::respond'. 2. Setup virtual server with backend server which sends a reset when connected. It can also be another BIG-IP with iRule. 3. From a client, try to access the backend server. 4. Server sends a reset.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips