WafMatchElementSubParser

JSON Example

{
    "index": 0,
    "match_case": "string",
    "match_element": "string",
    "match_op": "string",
    "sub_parser": "string"
}

integer As uint32 As uint32

index

Required

Determine the order of the rules. Field introduced in 31.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.

string

match_case

Optional

Constraints: default: SENSITIVE

Case sensitivity to use for the matching. Enum options - SENSITIVE, INSENSITIVE. Field introduced in 31.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.

string

match_element

Required

The match element for which a subparser can be specified. Allowed values are of the form 'ARGS name' where name can be any string or a regular expression. Field introduced in 31.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.

string

match_op

Optional

Constraints: default: EQUALS

String Operation to use for matching the match element name. Allowed values are EQUALS and REGEX_MATCH. Enum options - BEGINS_WITH, DOES_NOT_BEGIN_WITH, CONTAINS, DOES_NOT_CONTAIN, ENDS_WITH, DOES_NOT_END_WITH, EQUALS, DOES_NOT_EQUAL, REGEX_MATCH, REGEX_DOES_NOT_MATCH. Field introduced in 31.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.

string

sub_parser

Optional

Constraints: default: WAF_REQUEST_PARSER_AUTO_DETECT

Select the parser for this element. Allowed values are JSON, XML and AUTO_DETECT. Enum options - WAF_REQUEST_PARSER_URLENCODED, WAF_REQUEST_PARSER_MULTIPART, WAF_REQUEST_PARSER_JSON, WAF_REQUEST_PARSER_XML, WAF_REQUEST_PARSER_HANDLE_AS_STRING, WAF_REQUEST_PARSER_DO_NOT_PARSE, WAF_REQUEST_PARSER_AUTO_DETECT. Field introduced in 31.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.

Property Of

WafConfig