Thanks for the reply Jörg. I was under the impression that the `/` need to be in the sling:internalRedirects to pick up paths such as /apps, /etc, /libs and so on. If every path is prefixed with `/content/pathA/pathB` then I would be incorrectly rendering the previously mentioned paths.

All, I have internal redirects working as intended for our UAT, Stage, and Production sites when using a URL capture under /etc/maps.publish.(dev/stage/prod)/https i.e.<preprod.dc.example.cloud jcr:primaryType="sling:Mapping" sling:internalRedirect="[/,/content/pathA/pathB]"> </preprod.dc....