Bug ID 478920: SIP::discard is not invoked for all request messages

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Sep 11, 2014

Severity: 4-Minor

Symptoms

SIP::discard is invoked only for the first two request messages, and the other request messages are allowed to pass through.

Impact

Any iRule that uses SIP::discard might not work as expected.

Conditions

This occurs when an iRule that uses SIP::discard, for example: when SIP_REQUEST { SIP::discard }.

Workaround

To work around this issue, you can use MR::message drop in MR event to drop the message instead

Fix Information

The ingress queue for the messages is cleared properly when SIP::discard iRule is present. Now all request messages are correctly dropped if the SIP::discard iRule is present in SIP_REQUEST event.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips