Special characters in search terms:
Please note that the asterisk cannot be used when allowing or blocking words or phrases when using the 'Search terms' option in policies. This option is high lighted in red below:
The following special characters are not supported in Search Term allow and block lists.
| ¬ | £ |
Special characters in domains:
Within the Policy Allow lists there are various special characters that can be used to augment the URL and Keyword scanning which we can perform:
- A forward-slash (/) is allowed only with a valid FQDN pattern. This means that there must be at least one dot (.) before the first forward-slash (/) in a URL.
- Example of a valid entry: domain.com/abc
- Example of an invalid entry: domain/abc.xyz or domain/
- An entry cannot have a forward slash(/) and an asterisk (*).
- Example of an invalid entry: domain.com/abc*xyz
- an entry cannot include a question mark (?) and an equal to sign (=) in the path after the forward-slash (/).
- An example of an invalid entry: domain.com/abc=tyd or domain.com/abc?ytd
- Any entry with an ampersand (&) is not allowed.
- An example of an invalid entry: https://www.abc.com/search/?size=10&q=xy
The following special characters are not supported in URL allow and block lists when adding URL patterns:
- E,g, searchterm& is not supported but website.com/url/searchterm& is supported
| ! | " | £ | $ | % | ^ |
| & | ( | ) | = | + | { |
| } | [ | ] | ; | ' | @ |
| # | ~ | < | > | , | ? |
| \ | | | ` | ¬ |
To learn more about how to allow/deny a specific webpage on a website, click here.
Comments
Article is closed for comments.