We use SPS for reverse proxy services. The below is the request flow. I noticed "trailing slash problem" on the URLs behind the SPS. These URL are unprotected by SiteMinder. The issue is noticed while launching URL that are directories. I noticed http 301 redirect to downstream RHEL Apache server URL and the URL is also exposed to the end users which is not supposed to happen on a Reverse Proxy case. This RHEL Apache server URL is not public accessible so it always fails. The URL works fine if I add "/" at the end. But it is not feasible to tell end users to add "/" and also has problems while internally calling such URLs in application code. The below is the flow in a nutshell. Images are also attached for reference.
URL (browser) --> SPS --> RHEL Apache (hosted on different server) --> Page Displayed
Release : 12.7
Component : SITEMINDER -WEB AGENT FOR APACHE
"Handling Redirects by Destination Servers"
This is probably what you are looking for.
There is also "Default Virtual Host Values"
I noticed the following in your Access Gateway server.conf:
You might need to set:
This is so, in this case, redirects will not redirect the host portion of the URL.
You have many VirtualHosts and I cannot really evaluate the impact of changing this on all of them so you will need to test, and might need to use filteroverridepreservehost.
Customer specifically used:
<VirtualHostDefaults> ... enableproxypreservehost="yes" ... </VirtualHostDefaults> <VirtualHost name="<VIRTUALHOST>"> ... enableredirectrewrite="yes" redirectrewritablehostnames="ALL" ... </VirtualHost>