User Guide
WORKING WITH USER DEFINED END-USER NOTIFICATION PAGES
CHAPTER 12: NOTIFYING END USERS 249
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¶m2=value2
Table 12-4 describes the parameters AsyncOS includes in the query string.
Table 12-4 End-User Notification Parameters for Redirected URLs
Parameter Name Description
Time Date and time of the transaction.
ID Transaction ID.
Client_IP IP address of the client.
User Username of the client making the request, if available.
Site Host name of the destination in the HTTP request.
URI URL path specified in the HTTP request.
Status_Code HTTP status code for the request.
Decision_Tag ACL decision tag as defined in the Access Log entry that indicates how the
DVS engine handled the transaction.
For more information about ACL decision tags, see “ACL Decision Tags” on
page 439.
URL_Cat URL category that the URL filtering engine assigned to the transaction request.
For a list of the different URL categories, see “URL Category Descriptions” on
page 293.
Note: AsyncOS for Web sends the entire URL category name for both
predefined and user defined URL categories. It performs URL encoding on the
category name, so spaces are written as “%20”.
WBRS WBRS score that the Web Reputation Filters assigned to the URL in the
request.