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

I don't think so. You'll to extend this functionality for customization per your equirements.

Generally, organization use some vendors to identify the user's geo-location like DemandBase, ZoomInfo, KickFire, Terminus... 

Its really hard to know whats going on just from the above information. I would try below:1. Try in incognito or different browser and see if it occurs. Sometimes, browser plugins may cause this issue2. tail the error log and see if you can get more info. Thanks,Singaiah

I haven't tested on plain instance but seeing this issue on > 6.5.5

Looks like some structural changes on AEM 6.5. We've faced similar issues (not same as below) and modifying the predicates to fix these issues. Thanks,Singaiah