NSX-T Data Center Global Manager REST API
LBHttpRequestUriArgumentsCondition (type) (Deprecated)
{
"additionalProperties": false,
"deprecated": true,
"description": "This condition is used to match URI arguments aka query string of Http request messages, for example, in URI http://exaple.com?foo=1&bar=2, the \"foo=1&bar=2\" is the query string containing URI arguments. In an URI scheme, query string is indicated by the first question mark (\"?\") character and terminated by a number sign (\"#\") character or by the end of the URI. The uri_arguments field can be specified as a regular expression(Set match_type to REGEX). For example, \"foo=(?<x>\\d+)\". It matches HTTP requests whose URI arguments containing \"foo\", the value of foo contains only digits. And the value of foo is captured as $x which can be used in LBRuleAction fields which support variables.",
"extends": {
"$ref": "LBRuleCondition
},
"id": "LBHttpRequestUriArgumentsCondition",
"module_id": "PolicyLoadBalancer",
"polymorphic-type-descriptor": {
"type-identifier": "LBHttpRequestUriArgumentsCondition"
},
"properties": {
"case_sensitive": {
"default": true,
"description": "If true, case is significant when comparing URI arguments.",
"required": false,
"title": "A case sensitive flag for URI arguments comparing",
"type": "boolean"
},
"inverse": {
"default": false,
"required": false,
"title": "A flag to indicate whether reverse the match result of this condition",
"type": "boolean"
},
"match_type": {
"$ref": "LbRuleMatchType,
"default": "REGEX",
"required": false,
"title": "Match type of URI arguments"
},
"type": {
"$ref": "LBRuleConditionType,
"required": true,
"title": "Type of load balancer rule condition"
},
"uri_arguments": {
"description": "URI arguments, aka query string of URI.",
"required": true,
"title": "URI arguments",
"type": "string"
}
},
"title": "Condition to match URI arguments of HTTP requests",
"type": "object"
}