Operational Defect Database
BugZero found this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1498361
Custom HTTP::respond does not fire as part of custom connect-error-message in HTTP explicit proxy profile.
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP LTM
Affected releases:
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
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1498361: Custom HTTP::respond does not fire as part of custom connect-error-message in HTTP explicit proxy profile. ... Last Modified: Apr 26, 2024 ... 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.
