Applies To:
HTTP Large
HTTP Small
ADN
HTTP Rules Engine
There are several types of match options used to identify a request based on its URL path. This section identifies the key differences between each of these match options.
The following table indicates for each match option which parts of a URL can be matched and whether it supports the use of special characters when defining the match criteria.
| Name | Relative Path | File Name | File Name Extension | Special Characters | Regular Expressions |
|---|---|---|---|---|---|
| URL Path Regex |
|
|
|
|
|
| URL Path Wildcard |
|
|
|
|
|
| URL Path Literal |
|
|
|
||
| URL Path Directory |
|
|
|||
| URL Path Filename |
|
|
|
||
| URL Path Extension |
|
|
The following table provides additional tips on when you should use each match option.
| Name | Description |
|---|---|
| URL Path Regex | Use this match option to match URL paths using regular expressions. |
| URL Path Wildcard |
Use this match option to gain the most amount of flexibility without the use of regular expressions. |
| URL Path Literal | Use this match option to ensure that the request's relative path starts with the exact value assigned to this match option. |
| URL Path Directory | Use this match option to exclude filenames when matching against a request's URL. |
| URL Path Filename | Use this match option to find all requests that match a particular filename. |
| URL Path Extension | Use this match option to only match against the filename extension specified in the request. |