Bug ID 1189865: "Cookie not RFC-compliant" violation missing the "Description" in the event logs

Last Modified: Nov 02, 2023

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 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.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 17.0.0,,

Fixed In:
17.1.1, 16.1.4, 15.1.9

Opened: Nov 15, 2022

Severity: 4-Minor


When a request is blocked due to "Cookie not RFC-compliant' violation, the description field in the request log details is shown as "N/A" instead of having the description (for example "Invalid equal sign preceding cookie name" or "Invalid space in cookie name").


The description is empty and we can't know what is the problem with the request.


The violation is blocked due to "Cookie not RFC-compliant" violation and we are looking at the request log details.



Fix Information

After the fix, the description is shown in the request log details in the description field

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips