- "smithy.api#documentation": "<p>What WAF should do if it fails to completely parse the JSON body. The options are\n the following:</p>\n <ul>\n <li>\n <p>\n <code>EVALUATE_AS_STRING</code> - Inspect the body as plain text. WAF\n applies the text transformations and inspection criteria that you defined for the\n JSON inspection to the body text string.</p>\n </li>\n <li>\n <p>\n <code>MATCH</code> - Treat the web request as matching the rule statement.\n WAF applies the rule action to the request.</p>\n </li>\n <li>\n <p>\n <code>NO_MATCH</code> - Treat the web request as not matching the rule\n statement.</p>\n </li>\n </ul>\n <p>If you don't provide this setting, WAF parses and evaluates the content only up to the\n first parsing failure that it encounters. </p>\n <p>WAF does its best to parse the entire JSON body, but might be forced to stop for\n reasons such as invalid characters, duplicate keys, truncation, and any content whose root\n node isn't an object or an array. </p>\n <p>WAF parses the JSON in the following examples as two valid key, value pairs: </p>\n <ul>\n <li>\n <p>Missing comma: <code>{\"key1\":\"value1\"\"key2\":\"value2\"}</code>\n </p>\n </li>\n <li>\n <p>Missing colon: <code>{\"key1\":\"value1\",\"key2\"\"value2\"}</code>\n </p>\n </li>\n <li>\n <p>Extra colons: <code>{\"key1\"::\"value1\",\"key2\"\"value2\"}</code>\n </p>\n </li>\n </ul>"
0 commit comments