Hello Suman,
We do not want to block any error message.
We used fiddler trace and found that it is the length of combined parameters which reports like Missing Time generates is blocking factor.
To fix it, we increased the length of UrlSegmentMaxLength on all the three servers in the Cluster.
As Rob already mentioned, it will run fine on one of the servers in the cluster but not all despite all servers being configured the same way.
So with 3 servers in our UAT cluster, 1 will run reports fine after the registry setting change but the other 2 will still throw a Bad URL error.
We want to fix this so that Users if redirected to any of these three servers, should be able to execute the report.
Already we have IIS server in front of Apache Tomcat. CA Siteminder does not have application agent for Apache Tomcat like they have for WebSphere.
Recommendation is to use IIS or Apache as WebServer, so that WebAgent can be deployed for Siteminder Authentication.
Hence not sure how Apache Reverse Proxy needs to be implemented here.
Kind Regards,
Abhijit