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

Geocoder plugin getting a 403 #1988

Closed
paoloalba opened this issue Aug 19, 2024 · 1 comment
Closed

Geocoder plugin getting a 403 #1988

paoloalba opened this issue Aug 19, 2024 · 1 comment
Labels
not our bug The bug cannot be fixed in folium but needs to be solved somewhere else plugin This issue/PR is about an existing or new plugin

Comments

@paoloalba
Copy link

I use the Geocoder plugin in my map, which happens not to work (403) when used from the .save() html file, but just on some machines. Comparing the traffic between the same map used in a jupyter notebook and the one from the file, I can only spot that the jupyter one has an Origin from the headers, while the file one is set to "null".
The problem appears only from the file version, in both Edge and Firefox.
I assume that if I would render the map within another app, e.g. Panel, the problem would not be present. Is there a way to make the file able to use the Geocoder?

@Conengmo Conengmo added bug An issue describing unexpected or malicious behaviour plugin This issue/PR is about an existing or new plugin labels Sep 10, 2024
@Conengmo
Copy link
Member

I'm unable to reproduce this issue unfortunately. You mentioned it only seems to happen on some machines.

Unfortunately there's not much we can do here. This Folium plugin wraps around a Javascript library: https://github.com/perliedman/leaflet-control-geocoder. Things like the HTTP requests are handled in that library. So I'm afraid you'll have to look there for a solution.

I'll close the issue since I don't think there's anything to be done in Folium. But if somebody finds out more about this, please also update us here.

@Conengmo Conengmo closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
@Conengmo Conengmo added not our bug The bug cannot be fixed in folium but needs to be solved somewhere else and removed bug An issue describing unexpected or malicious behaviour labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not our bug The bug cannot be fixed in folium but needs to be solved somewhere else plugin This issue/PR is about an existing or new plugin
Projects
None yet
Development

No branches or pull requests

2 participants