Website kiosk wildcard URL allowlist: allow all paths under a base URLSolved

Hi @ronnie,

For Website Kiosk URL allowlisting, you can allow all sub-URLs under a base website by adding the base URL with a trailing “/”. For example, instead of only adding https://example.com, you can add https://example.com/.
This allows URLs that come after that base path, such as https://example.com/page1 and https://example.com/folder/page2.

If the kiosk shows a forbidden or blocked message, it usually indicates that the website is not included in the allowed websites list. However, if the page keeps loading without showing a blocked message, the URL is likely no longer being blocked by the kiosk allowlist, and the cause may be outside the kiosk policy.

Regards,
Sienna Carter
Hexnode UEM

That helps, the URL changed dynamically after the base URL. After adding the trailing slash, the forbidden message went away, but the page still keeps spinning.

Hi @ronnie,

In this case, the trailing slash is the important part for allowing paths under the base URL. If the behavior changes from a forbidden/blocked message to continuous loading, it usually means the kiosk restriction is no longer the blocker.

A good way to confirm this is to test the same URL on the device outside kiosk mode. If it still fails or keeps loading outside kiosk mode, the issue is more likely related to the website, authentication flow, network filtering, redirects, or another dependency required by the page.

Regards,
Sienna Carter
Hexnode UEM

Thanks, we tested the same URL without kiosk mode, and it looks like the issue is not policy-related. Adding the base URL with the trailing slash resolved the allowlist part; the remaining loading issue seems to be on the site/network side.