[BUG] New default maps service cached policy causing CORS issue

Describe the bug

We navigating to a new maps services maps.opensearch.org. Went trying to use it out of the box I keep getting a CORS issue when trying to access a visualization with maps. I had to manually clear my cache then I was able to see maps out of the box. It could potentially be we got some policy cached for the old service and when it attempts to make a call it is making a call with the old policy causing a CORS issue.

To Reproduce Steps to reproduce the behavior:

1. Have old service working
2. Create a viz with region maps
3. Notice map
4. Use new map service
5. Create a viz with region maps
6. Notice CORS issue

Expected behavior Maps works out of the box

OpenSearch Version 1.2

Dashboards Version 1.2

Plugins n/a

Screenshots n/a

Additional context

Need to verify if other folks are seeing this. And will add more content to this issue once I recreate it.

[dblock]

@tmarkley @kavilla I understand we changed something in a live configuration. That’s ok as an immediate workaround, but it’s not a fix. I’ll reopen until we confirm that the change made it into code (CDK or otherwise).

[AMoo-Miki]

Looking at the headers of the failure, we found that CORS headers were missing in the response from the CDN. That is even though the CDN was configured to respond with CORS headers and had been working fine.

One theory is that the failing file, v2.json, was requested in a non-XHR context and a CDN edge cached the response without the CORS headers. Subsequently, a request for the same file, when made via fetch, received the cached response from the CDN which didn’t contain the CORS headers.

Steps to reproduce:

1. Clear CDN cache
2. Open https://maps.opensearch.org/tiles/v2.json?osd_version=1.2&opensearch_tos_agree=true in your browser.
   • You should see the response has no CORS headers
3. Hit that URL with fetch in the console of the browser’s dev-tools:

   fetch("https://maps.opensearch.org/tiles/v2.json?osd_version=1.2&opensearch_tos_agree=true", {
    "referrer": "http://localhost:5602/",
    "referrerPolicy": "strict-origin-when-cross-origin",
    "body": null,
    "method": "GET",
    "mode": "cors",
    "credentials": "omit"
   });
   

   • You should see the response has no CORS headers even if you clear your browser’s cache.

Will continue to look for other explanations with refreshing the CDN cache.