Notifications > URL Access Override
A user receives the URL Access Override Mode notification if a user tries to access
a URL in a category that has a "block with override" action set by company policy.
The user receives the override warning and needs to enter a password to continue.
In the notification, the user sees the amount of additional time allowed for browsing.
After entering the correct password, the user continues to the requested Web page.
The user has an option to click one of the following links in the warning message:
The administrator must first set the category action in the policy to the "Time Limit"
or "Block with Override" action setting. See
URL Filtering Policies: Rules for details.
The configurable parameters in the URL Access Override Notification include:
-
Headline—Type the header line to appear in the browser. The default headline is Trend Micro InterScan Web Security Event. The headline is common for virus infection messages, file type blocking, and URL
blocking messages.
 |
Note
The %H variable can work in the headline. All other variables work in the body of
the message.
|
-
You can design your own notification page using any HTML editor; then Import the page to IWSVA (for example, if you want to display company brandings, or provide
a link to additional resources).
-
You can append a custom message to the IWSVA default by selecting both the Default and Customized options.
-
If you customize URL Access Override notifications, the message template must contain
some Java Script code to encrypt the password with base64 code. It should contain
some elements: password, time limit and ttl_type (in minutes or hours). Otherwise,
the customized notification page cannot work.
-
Example:
<form id="overridecontinue" method="post" action="%B[Warn and Continue URL/URI]$$$IWSX_URL_ACTION$$$">
<INPUT type=hidden value="%A[Action]" name=data>
..
</form>
-
A button or hyperlink must be defined to submit the form about the customized notification
for users to continue.
Example:
value="Submit" class="style3"
onclick="doSubmit();" />
See also: