Bug ID 680606: Using iRule HTTP::redirect or HTTP::respond inside HTTP_REQUEST causes connection reset.

Last Modified: May 01, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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

Fixed In:
14.0.0

Opened: Aug 28, 2017
Severity: 3-Major

Symptoms

When trying to run HTTP::redirect or HTTP::respond inside an HTTP_REQUEST event in which the destination host name is used (instead of an IP address), the HTTP connection is incorrectly reset.

Impact

HTTP connection is unexpectedly reset.

Conditions

-- iRule statement HTTP::redirect inside HTTP_REQUEST event. -- Use DNS name server to resolve the host name.

Workaround

None.

Fix Information

Using HTTP::redirect or HTTP::respond inside HTTP_REQUEST event no longer causes a reset.

Behavior Change