Forum Discussion
Deepak_21563
Nimbostratus
Feb 05, 2019JSON data format
Hi,
I am presently trying to solve an ASM block issues concerning JSON formatted data. We have a VIP to which a ASM policy is associated. This ASM policy has a XML and JSON profile added. The AS...
samstep
Cirrocumulus
Feb 05, 2019This is clearly an invalid JSON grammar, I have no idea how your customer is parsing this data.
Since the whole thing is in double-quotes it makes the whole structure a string, not JSON. So it fails RFC4627 straight away (JSON must start with an object, not a string).
If you remove the outer double-quotes:
{\"Inputs\":[{\"ATPONumber\":\"test12345\",\"CEPDay\":365}]}
then it fails both RFC4627 and RFC7159!
On a historical note - F5 ASM dates back to 2004 and RFC7159 was released in 2014, so I assume that F5 ASM's JSON parser is using RFC 4627 (F5 staff please confirm)
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects