CirrusHello,
A JSON profile was configured for an ASM policy but when a parameter with the "Null" value is detected, it triggered a Malformed JSON data violation.
I need to know why the "Null" value doesn't match the configured JSON profile, and how can i add this value to that profile ?
can anyone helps me to solve this problem ?
Thank you in advance.
Best regards
NacreousHi,
Are you trying "Null" or "null" in lowercase?
What BIG-IP version are you facing issue?
I tested on 14.1.2.2 and it works fine.
I simply create a policy, a JSON profile, a URL for this content and a parameter for that.
It works in default content profile, wildcard url and parameter as well
The only way that I've reproduced error is to not surround parameter names or alphanumeric values in quotes.
Content tested:
{ "id" : null }
OK
{ id : null }
Fail
{ "id" : Null }
Fail
{ "id" : "Null" }
OK / but it's null as word and not as char value
{ "id" : 0 }
OK
{ "id" : "abc123" }
OK
{ "id" : abc123 }
Fail
What values appears in your log entry as occurrence blocked?
Regards.