Bug ID 1004801: In the violation details for Max Parameter Protocol Compliance, the incorrect number of parameters is shown.

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,

Fixed In:

Opened: Mar 23, 2021
Severity: 4-Minor


Incorrect number of parameter is shown in the violation details for Max Parameter Protocol Compliance.


Request event displays inaccurate number of parameters: the maximum number, plus 1 (e.g., if you specify 7, the maximum shown will be 8). This occurs because the system stops parsing parameters when the violation is triggered, which occurs when receiving a request with more than the value specified in Max Parameter Protocol. So if you enable the alarm or block flag on requests with 5 parameters, a request with more than 5 parameters will be alarmed/blocked, and the number reported will be 6. If the system receives requests with more than 6 parameters, the number of parameters is still reported as 6.


Alarm or block flag is enabled on Max Parameter Protocol Compliance violation, and the request contains more than the maximum specified.



Fix Information

Instead of the number of parameters in the request, now the request event displays the configured max parameter value.

Behavior Change