How does redirection for blocked pages work?

When a request is blocked, Securly Filter can redirect those requests to a block page that is not hosted by Securly. This uses redirection, so the end user is still directed to the Securly block page but can then be forwarded elsewhere.

There is an order of precedence when multiple redirection policies overlap which is: 

Site > Category > Policy > Default page

The Default page is where all blocked requests can be redirected, other than that you can create redirection policies for Policies, Categories, and Sites.

It is possible to introduce a delay when redirecting users, this is advantageous when testing or when wanting to reveal to the user that Securly is redirecting their request.

When configuring a redirection URL, the following variables can be used:

%SITE% = Site, or domain name

%URL%' = base64 encoded full URL

%IP% = Client IP Address (public IP)

%KEYWORD% = Search terms, if present.

%USERNAME% = The username that we log

%POLICY% = The policy that is logged for this activity

%CATEGORY% = The category name

%REASON% = The descriptive reason from the block page