The current design of Custom Error Pages on SPS very very difficult and not thought through on paper.
From a documentation perspective, this is what we have Configure the Custom Error Pages Settings - CA Single Sign-On - 12.52 SP1 - CA Technologies Documentation
However it is unclear what components within the Secure Proxy Server does this configuration impact.
From an extensive research we did for a Customer, we found that the implementation model for the current Custom Error Pages is quite cumbersome task to implement.
I am going to explain this with one use case of 404 Page not found.
404 Page not found can occur within different layers of Secure Proxy Server.
- Apache WebServer Layer i.e. via JkUnMount.
- Anything which JkUnMount does not handled is handled via the ProxyEngine.
- WebApps layer within Tomcat e.g. affwebservices.
Our recent investigations found that following.
- The Custom Error Page settings in SPS ProxyUI / Server.conf is only applicable to ProxyEngine Layer.
- The Custom Error Page settings in SPS ProxyUI / Server.conf is not applicable to resources being served off Apache WebServer using JkUnMount (static HTML pages and images).
- The Custom Error Page settings in SPS ProxyUI / Server.conf is not applicable to 404 message being sparked off by a WebApp at Tomcat layer e.g. affwebservices.
Therefore we have manually go and update 3 different places to handle 404 Custom Error Pages.
Apache WebServer.... httpd.conf : This is not updated by the ProxyUI
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
ProxyEngine Layer.... *.properties files in Tomcat/properties folder : This is updated by the ProxyUI
Individual WebApps e.g. Affwebservices web.xml : This is not updated by the ProxyUI
"At present SPS is not handling the error page redirection this needs to be done manually with following configuration change in
Please be sure to make a backup before making this change.
Please modify web.xml in affwebservices deployment to include information like below in specific xml content under <web-app> element
<location>500 error specific page path</location> </error-page>
<location>404 error specific page path</location> </error-page>
<location>403 error specific page path</location> </error-page>
before doing above modification stop application server where affwebservices were deployed (i.e SPS )
After performing modification start application server where affwebservices were deployed (i.e SPS ).
SecureProxyServer is one component, therefore why does it feel it is so disjoint. Could it not be made better by referring all of the error pages to one central location under one central configuration. Therefore irrespective of which component OR code throws a 404, it has to refer back to a central configuration for 404. I as an Admin should not be tinkering at different places / each webapps in SPS to configure a 404 custom error response. This is not a good design, is very error prone, cumbersome and makes a wonderful product look non user friendly to configure.
Could it not be made better by exposing a container space within the SPS for error pages OR does the actual pages themselves need to be deployed outside the SPS somewhere else. Because though I know how to deploy a HTML page within SPS at the Apache layer using JkUnMount OR at the Tomcat layer using ContextPath - we don't seem to define a supported configuration for deployment of Error Pages themselves within SPS.