Section for setting up various filters restricting access of selected clients to the web interface of the application.
Access Restriction - IP Filter
Filter active
When active, access to the application will be restricted based on the specified IP ranges and the client’s IP address according to the list below.
(default: off)
List of Blocked Networks
A list of IP addresses and ranges (in CIDR notation) separated by line breaks. Clients with an IP address within the specified ranges will not have access to the application.
Access Restriction - Reverse Record
Filter active
When active, access to the application will be restricted based on the specified reverse records, which are compared to the reverse lookup of the client's IP address according to the list below.
(default: off)
List of Blocked Records
A list of blocked reverse records (or their parts) separated by line breaks. Clients with a reverse record containing any of the specified lines will not have access to the application.
Access Restriction - Country
Filter active
When active, access to the application will be allowed or restricted based on the client's country according to the following settings and list.
(default: off)
Filter Type
Blacklist mode - Clients accessing the application from the specified countries will not have access to the application.
Whitelist mode - Only clients accessing the application from the specified countries will have access to the application.
(default: blacklist)
List of Blocked/Allowed Countries
A list of blocked or allowed countries. Depending on the whitelist/blacklist type, clients accessing the application from any of the specified countries will/will not have access.
Access Restriction - User-Agent
Filter active
When active, access to the application will be restricted based on the HTTP User-Agent header according to the following list. If the User-Agent header contains a string from the list, access will be denied.
(default: off)
List of Blocked User-Agents
A list of blocked User-Agent strings (or their parts) separated by line breaks. The lines are compared with the HTTP User-Agent header, and if any are found in the header, access is denied.
0 Comments