datasette-leaflet 0.3
datasette-leaflet 0.3 was released, updating the plugin that bundles Leaflet so other Datasette plugins can depend on a single copy.
The change addresses a conflict with OpenStreetMap's tile usage policy, which asks that requests to its hosted tile server carry a referrer header. Datasette table pages were sending the Referrer-Policy: no-referrer HTTP header, so any plugin pulling tiles from OpenStreetMap through those pages was sending no referrer and breaching the policy.
Version 0.3 sets the referrer policy on the tile requests themselves to strict-origin-when-cross-origin. In practice that means a cross-origin tile call passes the host of the originating page but withholds the full path, which satisfies OpenStreetMap's expectation without exposing the specific page URL. Scoping the policy to the tile requests rather than the whole page also leaves Datasette's broader referrer behaviour untouched.
Why it matters: anyone running Datasette plugins that render OpenStreetMap tiles on table pages should upgrade to keep their tile traffic within OpenStreetMap's usage rules. For plugin authors, the release shows the bundled Leaflet dependency taking on responsibility for compliant tile requests, so they can rely on it rather than configuring referrer headers themselves.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Release: datasette-leaflet 0.3 OpenStreetMap have a very reasonable policy that hits to their hosted tile server should send a referrer header . Datasette table pages used the Referrer-Policy: no-referrer HTTP header, causing plugins that loaded tiles from OpenStreetMap to violate that policy. datasette-leaflet is the plugin that loads a bundled Leaflet so other Datasette plugins can depend on it. It now sets the referrer policy on the tile requests themselves to strict-origin-when-cross-origin , passing the host b