Restricted Domains
Supported In:
Limits navigation to ensure visitors cannot access certain internet domains or specific pages.
Default Value: [empty]
Using the Restricted Domains list will allow you to specify which domains and pages the visitor is not able to visit while using your kiosk. This can be used in conjunction with the Allowed Domains list to achieve finely-grained control.
In this article
How to add URLs
- Select 'Allowed Domains'.
- Select 'Edit' in the top navigation bar.
- Select the plus icon (+) from the bottom navigation bar.
- Enter a URL and select 'return'.
You can edit the URL again by touching anywhere in the white space. Touching the circle to the left of a URL will select it, allowing you to duplicate it or delete it. You can reorder URLs in the list by touching the list icon on the right of the URL and dragging up or down. You can also select or deselect all URLs.
If you select 'View' and touch a URL, Kiosk Pro will show you the components making up the URL:
If the allowed domains list is left blank, no restrictions will be placed on the browser and the visitor will be able to view any website they choose.
If you are limiting at the domain level, it is not necessary to prefix the domain name with http://
or www
. Kiosk Pro is only interested in the domain name itself.
URL format examples
'example.com' in the Allowed Domain list would allow access to:
http://www.example.com
http://www.example.com/index.html
(or any other page or folder following /)https://www.example.com
http://example.com
http://mobile.example.com
It is also possible to limit Kiosk Pro to specific prefix subdomains, so 'mobile.example.com' in the allowed domain list would allow access to:
http://mobile.example.com
and would not allow access to:
http://www.example.com
http://example.com
Wildcards
You can use wildcards (*) to stand in for certain parts of a URL. For example, *.edu
would allow any web address on a .edu
domain (like http://www.example.edu
).
Limiting to a folder or single page
You can also limit to a folder or individual page level. When limiting in these situations, you must include the full web address including http://
or https://
and wildcards if necessary.
http://www.example.com/subfolder/*
in the allowed domain list would allow access to:
http://www.example.com/subfolder/
http://www.example.com/subfolder/page.html
(or any other page or folder following /)
and would not allow access to:
http://www.example.com/subfolder2/
http://www.example.com/page.html
in the allowed domain list would allow access to:
http://www.example.com/page.html
and would not allow access to:
http://www.example.com/page2.html
https://www.example.com/page.html
Values for Remote Settings Control & Managed App Configuration
Key | kp_restrictedDomains |
---|---|
Key Type | string |
Default Value | [empty] |
Example | Use a semicolon to separate domains. For example: facebook.com;twitter.com |
Change Log
- Included in version 1.0. Updated key for Remote Settings Control & Managed App Configuration in version 10.0. The previous key ('blackList') has been deprecated, but will continue to work if using an older settings configuration.