This article applies to:

• WebMarshal

Question:

How do I create custom WebMarshal Error Pages?

Note: For information about policy block pages, see the following article:

• Q10248: How do I change Default Templates in WebMarshal?

Procedure:

It is possible to customize the notification pages returned by WebMarshal when an error is reported by the filtering engine or proxy server.

The files 'FilterError.htm' and 'ProxyError.htm' are installed into a subfolder of the WebMarshal installation as part of the standard install.

• WebMarshal 6.X and 7.X: The subfolder is on the Array Manager server, and is named Array Manager\Policy\Templates.
• When you commit WebMarshal Configuration, any changes to items in this folder are copied to each processing node server, and stored in the folder Node\Policy\Templates. New files and subfolders are also copied.
• You should only make changes to the Array Manager folder. The Node folders will be overwritten.

Edit these pages as desired to provide a custom look or additional help text.

When editing, take care to preserve the WebMarshal tags within these files. Make a safe backup of the original file before editing.

It is also possible to create customized pages for specific proxy errors (socket error, authentication failure, etc). For instance, it is possible to catch Windows password expiration and display a customized page with a link to an intranet site that allows a new password to be entered.

To create a custom error page, copy the standard error page to a new file called 'ProxyError<ErrorCode>.htm' (where <ErrorCode> is a standard windows error number). Examples of common error codes are:

• 1326 - Logon Failure (Bad user name or password)
• 1330 - Password Expired
• 10060 - Connection timeout

This article was previously published as:

NETIQKB29623

Marshal KB452