This article applies to:
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.
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
So to replace the password expiry page you would create a new page called ProxyError1330.htm.
When an error occurs WebMarshal will check first for an error specific page, followed by the generic ProxyError.htm, and finally the default template embedded inside WMProxy.exe.
- This article was previously published as:
- NETIQKB29623
- Marshal KB452
