Allied Telesis AR Series Technical Manual page 50

Configuring URL filtering
Rules for processing lists
The order of processing of lists is:

First—whitelists

Second—custom blacklists

Third—Kaspersky-provided blacklists
The matching logic is that as soon as a URL matches an entry in a list that it is being compared
against, then comparing stops and the relevant action (allow, if the match occurs in a whitelist, or
deny if the match occurs in a blacklist) is taken.
Because whitelist matching precedes blacklist matching, you can use custom whitelists to override
any corresponding blacklist entries. An HTTP or HTTPS request that has a URL matching an entry in
a whitelist will be permitted immediately, and the URL will not be matched against any blacklists.
So, if websites you actually want to access are being blocked by the Kaspersky blacklist, or some
subsection of an otherwise dangerous site is desirable, a whitelist may be created.
s ubs ec t For this example, the example.net/viruses/research folder contains information that is needed
within the otherwise completely blocked site.
This can be allowed by creating a whitelist file named 'whitelist-example.txt' in Flash memory, with
the contents:
example.net/viruses/research/*
And configuring it as follows:
awplus#configure terminal
awplus(config)#url-filter
awplus(config-url-filter)#whitelist whitelist-example.txt
awplus(config-url-filter)#protect
This whitelist will be processed prior to the blacklist, and will allow matching traffic through.
C613-22104-00 REV B
Advanced Network Protection
|
Configuring URL Filtering Page 50