Cisco Cisco Web Security Appliance S380 User Guide

Page of 824
Chapter 15      Notifying End Users
Working with User Defined End-User Notification Pages
15-14
Cisco IronPort AsyncOS 7.1 for Web User Guide
OL-23207-01
For example, the following text is some HTML code that uses %R as a conditional 
variable to check if re-authentication is offered, and uses %r as a regular variable 
to provide the re-authentication URL. 
Any variable included in Table 15-2, `Variables for Customized End-User 
Notification Pages,' on page 9 can
 be used as a conditional variable. However, the 
best variables to use in conditional statements are the ones that relate to the client 
request
 instead of the server response, and the variables that may or may not 
evaluate to TRUE instead of the variables that always evaluate to TRUE. For 
example, the %t variable (timestamp in Unix seconds plus milliseconds) always 
evaluates to TRUE, so there is little value in making an if-then statement based on 
it.
Working with User Defined End-User Notification 
Pages
When you choose end-user notification pages defined by someone in your 
organization, by default, AsyncOS redirects all blocked websites to the URL 
regardless of the reason why it blocked the original page. However, AsyncOS also 
passes parameters as a query string appended to the redirect URL so you can 
ensure that the user sees a unique page explaining the reason for the block.
AsyncOS passes the parameters to the web server as standard URL Parameters in 
the HTTP GET request. It uses the following format:
<notification_page_url>?param1=value1&param2=value2
 
%?R
<div align="left">
<form name="ReauthInput" action="%r" method="GET">
<input name="Reauth" type="button" 
OnClick="document.location='%r'"
id="Reauth" value="Login as different user...">
</form>
</div>
%#R