I don't think it does that. Mostly, we have very little/no control over the CM integrations. Thanks,Singaiah

Allowing CORS for their own internal/external domains is common practice

I was assuming both of these sites are hosted on same AEM server(s). If yes then you/IT should be able to allow to grab the resources on these domains (no CORS) at the Apache level.

I would use the same servlet for easy maintenance (even though you can have a redirect to a different servlet at CDN or dispatcher level) Same servlet and same query logic based on path (should pass in as a request param)If you are maintaining multiple sites then you've different farms tied to farm ...

I would use Apache Http Client.https://mvnrepository.com/artifact/org.apache.httpcomponents/httpclient The JAX-RS comes with additional dependencies (this download additional javax dependencies) which might have a conflict with Sling dependencies. Thanks,Singaiah

Try with either getServletPath() or getRequestUrl()/getRequestUri(). One of these should work.Thanks,Singaiah

Just a thought: Perform a thorough testing with the SDI. I would prefer writing a schedulers or other approaches instead of using SDI.

Check the encoding config on AEM and see if that helps: Go to Apache Sling Request Parameter Handling OSGI config and change the Default Parameter Encoding to "UTF-8" and see if this helps.

You should be redirecting these requests (ending with //) to 404 page at the apache/dispatcher level. Any specific requirement that you want to allow these pages?

There are different way to handle this.Load this using Tag Management tool i.e. Launch, GTM..etcHost this on DAM and use that reference. Make sure the downstream TTL is set on the headers so the browsers will get the update continuously.ThanksSingaiah