Cirrus
MVPYou can see https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-asm-implementations/adding-json-support-to-an-existing-security-policy.html as if you dissabled "Parse Parameters" then the JSON schema will be used and it is seperate from the Global policy settings and I think there is no option under the content profile to make it case not sensative.
CirrusThanks for response Nikoolayy1 .
I think that you point to the follow section:
After a JSON schema is uploaded and selected, the Parse Parameters setting is disabled because the policy stops using any configured policy parameters and begins using the custom JSON parameters from the JSON schema file(s).
I understood what you mean but JSON schema is still under policy which is case-insensitive. It's correct that parameters are taken from schema instead policy configuration but should global parameters (like case- (in)sensitive) be excluded as well?