How does it work?
This criterion lets you match based on the URL directory path. The path must start with a /.
Operators
You can select the following logical conditions:
| Value | The Rule is True When… |
|---|---|
| matches one of | the incoming request includes any of the specified paths. |
| does not match one of | the incoming request doesn’t include any of the specified paths. |
Fields
In the text field, enter the URL path starting with a “/ “. The path is relative to the server root, for example, /blog. The match excludes leading hostname and trailing query parameters if present in the request.
Wildcards
The Path match supports the following wildcards:
| Wildcard | Description | Example |
|---|---|---|
| * | matches zero or more characters | The rule includes a match where the path value is /*/my_path/ *. Some possible valid results for this wildcard is /blog/my_path/2014 . |
| ? | matches a single character | The rule includes a match where the hostname value is /blog/my_path/201? . Some possible valid results are: /blog/my_path/2016 or /blog/my_path/2017 . |
Additional Options
- Case-sensitive: If you select this option, the file name in the incoming request has to match the case of the entry.
- Normalize path: Select this option to automatically modify the string that identifies a path or file so that it conforms to a valid path on the target operating system.