EdgeVirtualServiceHttpResponseMatchCriteria
Defines a response match criteria. If multiple matches are configured, it is treated as logically AND operation. All match types must be true for the response match criteria to be satisfied.
{
"clientIpMatch": {
"matchCriteria": "string",
"addresses": [
"string"
]
},
"servicePortMatch": {
"matchCriteria": "string",
"ports": [
0
]
},
"methodMatch": {
"matchCriteria": "string",
"methods": [
"string"
]
},
"protocol": "string",
"pathMatch": {
"matchCriteria": "string",
"matchStrings": [
"string"
]
},
"queryMatch": [
"string"
],
"cookieMatch": {
"matchCriteria": "string",
"key": "string",
"value": "string"
},
"locationHeaderMatch": {
"matchCriteria": "string",
"value": [
"string"
]
},
"requestHeaderMatch": [
{
"matchCriteria": "string",
"value": [
"string"
],
"key": "string"
}
],
"responseHeaderMatch": [
{
"matchCriteria": "string",
"value": [
"string"
],
"key": "string"
}
],
"statusCodeMatch": {
"matchCriteria": "string",
"statusCodes": [
"200",
"302",
"400-450"
]
}
}
Defines match criteria based on HTTP or HTTPS protocol.
Defines match criteria based on query strings which are in key=value format.
Defines an HTTP match criterion for a specific header.
Defines match criteria based on the request headers.
Defines match criteria based on the response headers.
Defines an HTTP response status code match criterion. HTTP response codes are grouped into following five categories:
- Informational responses (100 ? 199).
- Successful responses (200 ? 299).
- Redirection messages (300 ? 399).
- Client error responses (400 ? 499).
- Server error responses (500 ? 599).