You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stop sending a referrer, and keep CARTO on the fallback for now
The only referrer a browser can send is its origin, and for a Nabu Casa
instance that origin is a per-installation identifier. Sending it to a
third party on every tile request is not a trade we want to make, and it
turns out we do not have to: measured across several tiles and the
TileJSON, vector.openstreetmap.org serves a browser with no Referer at
all. So the vector layer sends none, and `transformRequest` goes with it.
The raster fallback is the half that did need one. OSM's raster tiles
block a refererless browser - with HTTP 200 and a PNG reading "Access
blocked", so nothing would even look broken - and a browser cannot set a
User-Agent instead. Rather than leak the origin for the devices least
able to choose, that path keeps CARTO: for them it is not a regression,
it is exactly what they see today, overlay and all.
Both halves are temporary. Once maps.home-assistant.io proxies with a
real application User-Agent, there is no referrer anywhere and the
fallback moves to OSM raster with it.
CARTO serves @2x, so retina tablets get sharp tiles at the same request
count, where Leaflet's `detectRetina` would have fetched a zoom deeper at
four times the requests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments