Bug ID 429827: iRule recv command may return timeout while the data are actually received

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
10.2.1, 11.4.1

Fixed In:
11.5.0

Opened: Sep 05, 2013
Severity: 3-Major
Related AskF5 Article:
K15207

Symptoms

When you use the following iRule command the recv_status variable value is "timeout" regardless of whether the data received is good or not: recv -peek -status recv_status -timeout 0 $test_sideband_IP

Impact

The good data get discarded.

Conditions

When using the command, you use the "timeout -0" option. The data are received just before the timeout.

Workaround

Use 11.5 build.

Fix Information

recv command now checks timeout after check data received so good data received just before timeout is not discarded.

Behavior Change