Skip to content

Conversation

@bplubell
Copy link

@bplubell bplubell commented Sep 15, 2025

Per the Nominatim usage policy, all requests should have an identifying Referer or User-Agent header (quoted below). Using the host name, as we already do for Mapbox requests, should be sufficient to satisfy the requirement while avoiding the need for additional settings.

Provide a valid HTTP Referer or User-Agent identifying the
application (stock User-Agents as set by http libraries will not do).

Based on a recommendation from an openstreetmap.org system administrator, I also added the identifier to the User-Agent header. My inference was that they block requests using it and having an app identifier would make it less likely we are blocked by another user that happens to be using the same User-Agent.

Per the [Nominatim usage policy][1], all requests should have an
identifying Referer or User-Agent header (quoted below). Using the host
name, as we already do for Mapbox requests, should be sufficient to
satisfy the requirement while avoiding the need for additional settings.

> Provide a valid HTTP Referer or User-Agent identifying the
> application (stock User-Agents as set by http libraries will not do).

[1]: https://operations.osmfoundation.org/policies/nominatim/
An openstreetmap.org system administrator recommended we include an app
identifier in the User-Agent header. My inference is that they block
based on the User-Agent. However, I did not want to use only the app
identifier so I found the form that Craft uses and copied that,
appending the app identifier.
@bplubell bplubell force-pushed the v4-nominatim-referer-header branch from aa6f7ea to a48b80d Compare September 17, 2025 21:39
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

Successfully merging this pull request may close these issues.

1 participant