End-of-Life (EoL)

URL Filtering Response Pages

The firewall provides three predefined response pages that display by default when a user attempts to browse to a site in a category that is configured with one of the block actions in the URL Filtering Profile (block, continue, or override) or when Safe Search Enforcement is enabled:
  • URL Filtering and Category Match Block Page
    —Access blocked by a URL Filtering Profile or because the URL category is blocked by a security policy.
  • URL Filtering Continue and Override Page
    —Page with initial block policy that allows users to bypass the block by clicking
    . With URL Admin Override enabled, (Configure URL Admin Override), after clicking
    , the user must supply a password to override the policy that blocks the URL.
  • URL Filtering Safe Search Block Page
    —Access blocked by a security policy with a URL filtering profile that has the Safe Search Enforcement option enabled (see Enable Safe Search Enforcement). The user will see this page if a search is performed using Google, Bing, Yahoo, or Yandex and their browser or search engine account setting for Safe Search is not set to strict.
You can either use the predefined pages, or you can Customize the URL Filtering Response Pages to communicate your specific acceptable use policies and/or corporate branding. In addition, you can use the Table 1 for substitution at the time of the block event or add one of the supported Table 2 to external images, sounds, or style sheets.
URL Filtering Response Page Variables
The firewall replaces the variable with the username (if available via User-ID) or IP address of the user when displaying the response page.
The firewall replaces the variable with the requested URL when displaying the response page.
The firewall replaces the variable with the URL filtering category of the blocked request.
HTML code for displaying the
button on the URL Filtering Continue and Override page.
You can also add code that triggers the firewall to display different messages depending on what URL category the user is attempting to access. For example, the following code snippet from a response page specifies to display Message 1 if the URL category is games, Message 2 if the category is travel, or Message 3 if the category is kids:
var cat = "<category/>"; switch(cat) { case 'games': document.getElementById("warningText").innerHTML = "Message 1"; break; case 'travel': document.getElementById("warningText").innerHTML = "Message 2"; break; case 'kids': document.getElementById("warningText").innerHTML = "Message 3"; break; }
Only a single HTML page can be loaded into each virtual system for each type of block page. However, other resources such as images, sounds, and cascading style sheets (CSS files) can be loaded from other servers at the time the response page is displayed in the browser. All references must include a fully qualified URL.
Response Page References
Reference Type
Example HTML Code
<img src="http://virginiadot.org/images/Stop-Sign-gif.gif">
<embed src="http://simplythebest.net/sounds/WAV/WAV_files/ movie_WAV_files/ do_not_go.wav" volume="100" hidden="true" autostart="true">
Style Sheet
<link href="http://example.com/style.css" rel="stylesheet" type="text/css" />
<a href="http://en.wikipedia.org/wiki/Acceptable_use_policy">View Corporate Policy</a>

Recommended For You