7.9 Notifying Users with Notification Pages

WebMarshal uses web pages to provide pre-configured notification messages to users. The notifications can also be customized.

7.9.1 Notification Web Pages

When a user requests a Web resource that triggers a rule, they may receive a notification web page. The notification could simply state that a request was denied, or it could request acknowledgement of a warning before processing the request.

The choice of notification pages is made on the Action page of each rule wizard. Choices vary according to the type of rule.

7.9.2 Default Notification Pages

WebMarshal is supplied with a number of default notification pages. The files are standard HTML pages, located in the \ArrayManager\Policy\Templates sub-directory of the WebMarshal installation directory on the Array Manager server.

•Page Blocked–for denied web pages and other items where no part of the file was returned to the browser.

•Standard

•AdvertisingSmall (used in default rules for advertising sites)

•Blank (used for images)

•Offensive (for offensive content)

•Small

•With Sound (audible warning)

•File Aborted–for denied file type or size, where a portion of the file was returned to the browser.

•Standard

•Malicious (Malware content)

•Virus (virus content)

•File Blocked–for denied file type or size.

•Standard

•Malicious (Malware content)

•TextCensor (lexical scan found denied content)

•TextCensor Offensive (lexical scan found offensive content)

•Virus (virus content)

•GoogleWebRisk–used by the Google Web Risk policy. Any custom versions of these pages must include the Google disclaimer.

•GoogleWebRiskBlocked

•GoogleWebRiskWarning

•Quota–for quota rules.

•Quotas (displays the user’s quota)

•Quota Exceeded

•Quota Extend (allows the user to request an extension)

•TRACEnet–used by the TRACEnet policy.

•TRACEnet Blocked

•ReclassifyThanks (acknowledges the user’s request to reclassify a blocked item)

•Upload Blocked–for upload rules.

•Standard

•Malicious (Malware content)

•TextCensor (lexical scan found denied content)

•Virus (virus content)

•Warning–before access to “permitted with warning” sites.

•Standard

•Malicious (Malware content)

•Offensive (lexical scan found offensive content)

•Policy (for policy display rules)

•Previous Scan (site was placed in a URL category by a previous scan)

•Quotas (states that access is subject to quota)

•TextCensor (lexical scan found questionable content)

7.9.3 Editing Notification Pages

You can create new versions of the warning/blocking pages, or modify the existing pages.

Use HTML editing software to create or modify warning/blocking pages.

There are several types of warning/blocking pages, each identified by a filename prefix. New page names must start with one of the defined prefixes. The page types are as follows:

•Aborted–used when blocking websites where a portion of the file has been returned to the browser.

•Blocked–used when blocking websites.

•Warning–used to prompt the user before permitting access to a site.

•FileBlocked–used when a file is blocked by a file type or malware rule.

•UploadBlocked–used when a file upload is blocked.

•QuotaExceeded–used when a WebMarshal quota has been exceeded by the user.

•QuotaExtend–used to allow the user to extend a quota.

For example, to create a new blocking page for pornographic content, copy the file Blocked.htm to a new file BlockedPorn.htm. From then on, BlockedPorn.htm is available in the list of blocking pages when editing a site rule.

Please note the following important recommendations before editing the warning/blocking pages.

•Do not change the original page; instead, copy the file and make any changes to the copy.

•After changing pages, test them to make sure that they are still functioning correctly. Several pages include special forms that process user input; amending such a page may affect the prompting func­tionality.

•If you want to refer to the \Templates sub-directory, use the virtual domain name “webmar­shal.home.” For example, a link to a file placed in the \Templates sub-directory could be:

<image src= “http://webmarshal.home/blocked.gif”>

•Files over 32KB in size (such as a company policy document) should not be served from the Tem­plates sub-directory, to avoid deadlock problems with configuration updates. Host large files on another server/site.

•If you make links to other sites, ensure that these links are full URLs, not relative paths. WebMarshal replaces the content returned from websites with the warning/blocking pages. If you use a relative path, the link will refer back to the original blocked site