Understanding Redirection for Blocked Pages

When a request is blocked, Securly Filter can redirect those requests to a block page that is not hosted by Securly. This redirection allows the end user to be directed to the Securly block page, which can then forward them elsewhere.

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

• Site
• Category
• Policy
• Default page

The Default page is where all blocked requests can be redirected. In addition, you can create specific redirection policies for Policies, Categories, and Sites.

It is possible to introduce a delay when redirecting users. This feature is advantageous for testing purposes or when you want to inform the user that Securly is redirecting their request.

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

%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