What are the rules and restrictions of using *, . ,? , &, =, and / in the Allow/Block list for Global or Custom Policies?

Securly lets you add various keywords and URLs to the Allow/Deny list to help you customize filtering for your students. Here are some rules to consider when adding URLs with special characters to the Allow/Block list for Global or Custom Policies.

1. 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.
1. Example of a valid entry: domain.com/abc
2. Example of an invalid entry: domain/abc.xyz or domain/
2. A forward-slash (/) and an asterisk (*) cannot co-exist in an entry.
1. Example of an invalid entry: domain.com/abc*xyz
3. The entry cannot include a question mark (?) and an equal to sign (=) in the path after the forward-slash (/).
1. An example of an invalid entry: domain.com/abc=tyd or domain.com/abc?ytd
4. Any site with an ampersand (&) is not allowed.
1. An example of an invalid entry:  https://www.abc.com/search/?size=10&q=xy

To learn more about how to allow/deny a specific webpage on a website, click here.