Match Conditions
Last update：2024-06-13 19:18:16
By defining match conditions, implement the request features to be detected by the specified security policy. Custom Rules, Rate Limiting, Whitelist, and other security policies use the same configuration structure. This page lists all currently available matching condition fields.
Supported field
| Field | Description | Supported Operator | Case-Sensitive Match |
Supports Multiple Match Values |
|---|---|---|---|---|
| IP/CIDR | Match or exclude specific client IP addresses, supporting both IPv4 and IPv6. | equals | - | yes |
| does not equal | - | yes | ||
| Path | Match the rules based on the specific path contained in the request. The path starts with "/", does not contain domain name and parameter information, for example: www.test.com/common/ecs/channel?code=1&type=2, the path is /common/ecs/channel. | equals | yes | yes |
| does not equal | yes | yes | ||
| contains | no | yes | ||
| does not contain | no | yes | ||
| starts with | no | yes | ||
| ends with | no | yes | ||
| wildcard match | no | yes | ||
| wildcard mismatch | no | yes | ||
| regex match | no | no | ||
| regex mismatch | no | no | ||
| URI | Match the rules based on the specific URI contained in the request. The URI starts with "/", contains parameter information, for example: /common/ecs/channel?code=1&type=2. | equals | yes | yes |
| does not equal | yes | yes | ||
| contains | no | yes | ||
| does not contain | no | yes | ||
| starts with | no | yes | ||
| ends with | no | yes | ||
| wildcard match | no | yes | ||
| wildcard mismatch | no | yes | ||
| regex match | no | no | ||
| regex mismatch | no | no | ||
| User-Agent | Match the rules based on the value of User-Agent. | equals | yes | yes |
| does not equal | yes | yes | ||
| contains | no | yes | ||
| does not contain | no | yes | ||
| does not exist or has no value | - | - | ||
| starts with | no | yes | ||
| ends with | no | yes | ||
| wildcard match | no | yes | ||
| wildcard mismatch | no | yes | ||
| regex match | no | no | ||
| regex mismatch | no | no | ||
| Referer | Match the rules based on the value of Referer. | equals | yes | yes |
| does not equal | yes | yes | ||
| contains | no | yes | ||
| does not contain | no | yes | ||
| does not exist or has no value | - | - | ||
| starts with | no | yes | ||
| ends with | no | yes | ||
| wildcard match | no | yes | ||
| wildcard mismatch | no | yes | ||
| regex match | no | no | ||
| regex mismatch | no | no | ||
| Request Header | Match the rules based on the value of a specific request header (the case of the request header name is insensitive). | equals | yes | yes |
| does not equal | yes | yes | ||
| contains | no | yes | ||
| does not contain | no | yes | ||
| does not exist or has no value | - | - | ||
| starts with | no | yes | ||
| ends with | no | yes | ||
| wildcard match | no | yes | ||
| wildcard mismatch | no | yes | ||
| regex match | no | no | ||
| regex mismatch | no | no | ||
| Request Method | Match or exclude specific request methods. | equals | - | - |
| does not equal | - | - | ||
| Geo | Match or exclude requests from specific regions. | equals | - | - |
| does not equal | - | - | ||
| Response Code | Match or exclude requests with specific status codes. Only the status codes in the response stage are counted. | equals | - | - |
| does not equal | - | - |
Is the content of this document helpful to you?
Yes
I have suggestion