The SPS supports the custom error pages feature, which lets you customize the error pages that the Web Server displays when a client request fails.
The custom error pages section has the following format:
<customerrorpages>
#possible values are: "yes","no"
#default value is "no"
enable="no|yes"
#custom error pages implementation class
class="com.netegrity.proxy.errorpages.ErrorPageImpl"
#defines type of locale.
#possible values are: "0" (for Server specific), "1" (for Browser specific)
#default value is "0"
locale_type="0|1"
#this value should be the language code that will be understood by the java
#locale object, say "zh" for Chinese, "fr" for French, "es" for Spanish, "en" for
#english, etc.
#default value is "en"
locale_language="en"
#this value should be the country/region code that will be understood by the
#java locale object, say "CN" for China, "CH" for Switzerland, "AR" for
#Argentina, "US" for United States.
#default value is "US"
locale_country="US"
#display the complete call stack for exceptions
#possible values: "true" or "false".
#default value: "false"
showcallstack="true"
</customerrorpages>
Specifies how the SPS manages the web server error pages. If the value is set to yes, you can customize the Web Server error pages and the Web Server displays the customized error pages when a client request fails. If the value is set to no, the Web Server displays the default HTTP 1.1 error pages when a client request fails. The SPS reads the value at the startup.
Default: no
Specifies the locale of the custom error pages. If the value is set to 0, the SPS uses the locale settings of the SPS server to display the custom error messages. If the value is set to 1, the SPS uses the locale settings of your browser to display the custom error messages.
Default: 0
Specifies if the call stack must be retrieved to track exceptions that you want to debug. If the value is set to yes, the SPS retrieves the call stack and displays it on the custom error page. If the value is set to false, the call stack is hidden.
Default: false
Important! For security reasons, we highly recommend that you do not enable the showcallstack option unless you want to track the complete details of an exception that you want to debug. Disable showcallstack after you complete debugging.
| Copyright © 2012 CA. All rights reserved. |
|