Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Sep 11, 2014 Severity: 4-Minor
SIP::discard is invoked only for the first two request messages, and the other request messages are allowed to pass through.
Any iRule that uses SIP::discard might not work as expected.
This occurs when an iRule that uses SIP::discard, for example: when SIP_REQUEST { SIP::discard }.
To work around this issue, you can use MR::message drop in MR event to drop the message instead
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.