I have a leaflet map on a html page I use to show certain geopositioned assets from my database. One of the features uses nominatim reverse query for certain user actions. The actions that end in nominatim query are less than one per second, even less than one per minute. It works perfectly when run on my localhost, and when run from a test server. But when I put my page on my sharepoint server all the nominatim queries end with a 429 Too Many Requests response. The requests come from jQuery code executed on the browser, either firefox or chrome. For simplifying and making the point, let's say that the code is run in a click handler of the map
and the reverse geocoding function just invokes the url with a jsonp wrap
This code is in the page, and the page is in a private document library in my private sharepoint site hosted by microsoft office365 and accessed as xxxxxx.sharepoint.com What can I do to solve this limitation? asked 18 Dec '17, 10:19 P A |
In contrast to Firefox and Chrome, your sharepoint server likely does not send a HTTP referrer or user agent as requested by Nominatim's usage policy. You will need to consult the sharepoint documentation and/or contact your hoster to find out how to change that. Once a proper referrer/user agent is set, the error will go away. answered 03 Jan '18, 11:58 lonvia |
So the Nominatim queries always originate from the user and not from the server?
I have updated my question with more information on the code