Bug ID 572519: More than one header name/value pair not accepted by ACCESS::respond

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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

Fixed In:
13.1.0

Opened: Feb 08, 2016
Severity: 3-Major

Symptoms

An error is seen when ACCESS::respond command is used, for example, in an iRule with multiple header name/value pairs. The error appears similar to the following: warning: [The following errors were not caught before. Please correct the script in order to avoid future disruption. "unexpected token(s):....

Impact

An error is generated when the command is used.

Conditions

When ACCESS::respond command is used with multiple header name/value pairs.

Workaround

Let the command take only one name/value pair.

Fix Information

The ACCESS::respond iRule event has been corrected to accept multiple HTTP header name/value pairs in a similar way to HTTP::respond. For example: ACCESS::respond 200 content "http body" header1 value1 header2 value2

Behavior Change