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

known issue: Chrome local developer cross-origins error for GeoJSON #52

Open
JackDougherty opened this issue Nov 23, 2016 · 1 comment
Assignees

Comments

@JackDougherty
Copy link
Collaborator

We may not be able to fix this, so make a note to warn novice mapmakers:

If testing the map on a local computer (rather than GitHub Pages), use Firefox browser, because Chrome generates a cross-origins error for polygon GeoJSON

@JackDougherty
Copy link
Collaborator Author

Ilya's notes about the underlying problem:
Leaflet ‘forces’ http instead of https when using maps locally on your computer, as your local machine is an insecure location and HTTPS does not work with it, so leaflet is trying to be ‘smart’ about it and removes ’s'. Carto, however, has two completely different URLs for the two protocols, so the basemap is not loaded.

Chrome loves the new URL when it’s loaded from https (so from github it works perfect), however it will never let you get those maps from Carto to your local machine. I will see if I can tweak the plugin so that it can handle two URLs (http for local, https for secure origins).

@JackDougherty JackDougherty self-assigned this Dec 2, 2016
@JackDougherty JackDougherty changed the title cross-origins error for GeoJSON polygons on Chrome local file known issue: Chrome local developer cross-origins error for GeoJSON Mar 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant