Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem in the response - CORS error (new since a few days) #1793

Open
Wikinaut opened this issue May 2, 2024 · 2 comments
Open

Problem in the response - CORS error (new since a few days) #1793

Wikinaut opened this issue May 2, 2024 · 2 comments
Labels

Comments

@Wikinaut
Copy link

Wikinaut commented May 2, 2024

grafik

@Wikinaut Wikinaut added the bug label May 2, 2024
@Wikinaut
Copy link
Author

Wikinaut commented May 2, 2024

grafik

@Wikinaut Wikinaut changed the title CORS error (new since a few days) Problem in the response - CORS error (new since a few days) May 2, 2024
@yohanboniface
Copy link
Member

Hi @Wikinaut

The error you point to in the console is unrelated, it's the Sentry call that is blocked by your browser. Sentry is an anonymous error tracker, that help us get more context when an error occurs.

If I load your map, I see errors for three datalayers:

image

The first and the third are datalayers URL with old (< 1 month ago) schema. Those URLs should have been replaced by new ones during the migration, but obviously are not in this case. Has this map been imported recently, which could explain ?

The second one point to a missing file in the server. The server is looking at the file my-data.geojson, on a very old map. This file name is a very old pattern (from years ago), and is missing since #1003. The datalayer is "Kiezblock politisch beschlossen". Is this layer supposed to point on a file that old ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants