Bug ID 584310: TCP:Collect ignores the 'skip' parameter when used in serverside events

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2 HF1, 11.6.3.2, 11.5.4 HF3

Opened: Mar 30, 2016

Severity: 3-Major

Related Article: K83393638

Symptoms

When TCP::Collect is used with 'skip' and 'length' arguments in SERVER_CONNECTED, the "skip' argument does not take effect and is ignored. The Collect works, but collects only the length bytes from start.

Impact

TCP:Collect collects bytes without taking into account the skip, so the bytes collected are not the correct ones.

Conditions

TCP:Collect on server side events like SERVER_CONNECTED used with the 'skip' parameter. This is an intermittent issue that have happen only with IIS server.

Workaround

None.

Fix Information

The settings for TCP::Collect command skip and length arguments are now honored during packet processing.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips