Previous Topic: Notes for Custom 401 Pages

Next Topic: Manage User Access with IIS

How to Set Up Error Handling

To direct the Web Agent to a server error, access denied, require cookie, or cross-site scripting (CSS) custom error file or page, specify the file path or URL in the ServerErrorFile, Custom401ErrorFile, ReqCookieErrorFile, or CSSErrorFile parameters respectively. The error files can reside anywhere in your application.

Important! Any URL you configure as a custom error page should be an unprotected resource. To prevent a misconfiguration in which it is not possible to display the specified error file because it is protected, any URL you configure as an error page is added to the ignoreURL list.

Note: If your applications require URLs that include HTML tags, you can encode these characters so the Web Agent does not block a request. For information about encoding HTML characters, see: http://www.cert.org/tech_tips/.

The following examples show a file path and a URL to an error file. The syntax in the example is for a local Agent configuration file. These parameters can also be set in an Agent Configuration Object.

File Path:

CSSErrorFile="C:\error\error.txt"

ReqCookieErrorFile="C:\custompages\error.txt"

ServerErrorFile="C:\error\error.txt"

Custom401ErrorFile="C:\error\accessdenied.txt"

URL:

CSSErrorFile="http://www.mycompany.com.error.jsp"

ReqCookieErrorFile="http://www.myorg.com.error.asp"

ServerErrorFile="http://www.mycompany.com.error.jsp"

More Information

Custom Error Handling For Applications


Copyright © 2010 CA. All rights reserved. Email CA about this topic