Then go to another page such as https://linkedconnections.org, op the console, and execute this: fetch('https://tiles.openplanner.team/planet/14/8411/5480/').then(reponse => { console.log('yes')}); → You will see that it fails due to CORS as it does not contain the access-control-allow-origin: * header.
Try he same line but with a different tile that’s not yet in the server cache: fetch('https://tiles.openplanner.team/planet/14/8409/5410/').then(reponse => { console.log('yes')}); and see that this works.
My console log
It may be safe, as this is an open data server, to mark all responses, whether it’s a 500, 400, 300 or 200 with the same header in the NGINX config.
This is fixed now, I enabled CORS only at the NGINX level now for everything. I verified this using the same steps to reproduce as above, feel free to reopen if there is still an issue.
Sometimes, I suspect due to caching, certain tiles do not have a cross origin resource sharing header set correctly
Reproduce
fetch('https://tiles.openplanner.team/planet/14/8411/5480/').then(reponse => { console.log('yes')});
→ You will see that it fails due to CORS as it does not contain theaccess-control-allow-origin: *
header.fetch('https://tiles.openplanner.team/planet/14/8409/5410/').then(reponse => { console.log('yes')});
and see that this works.My console log
It may be safe, as this is an open data server, to mark all responses, whether it’s a 500, 400, 300 or 200 with the same header in the NGINX config.