Forum Discussion
Altostratusillegal cookie length: ASM violation
Nimbostratus8192 Is indeed the maximum and I think you only have 2 workarounds - disable the violation, or write a custom iRule. Disabling the violation itself would probably make the most sense here.
Go to policy blocking settings, and un-tick the 'learn/alarm/block' boxes under
Illegal cookie length
MSZWhat about 2048 bytes
- Hannes_Rapp
@MSZ - Can't understand the question
- MSZ
when I created the ASM policy longtime back I didn't notice the value of Max. cookie header length (It comes on Policy properties page). As per documentation it is any by default. But in my case I am able to see the value like 2048. I want to know how this value comes and where ?
- Hannes_Rapp
What is the current ASM version, and was the software version same when the policy was first created? The defaults vary across versions. I'd speculate that you may have created the initial policy on software where the default was indeed 2K, and later upgraded to software where the default is any. In that scenario, your 2K config would be retained.
- MSZ
Yes, the previous version was 11.6.1 and now its 13.0.0 Can we change the setting? Is it not harmful for the application?
