fix(map): send referrer with tile requests - #4338
Conversation
OpenStreetMap now blocks web tile requests without a valid Referer header. Set a per-tile referrer policy so local environments still identify their origin when loading the HTTPS tile service, even if the page-level policy is restrictive.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe map tile layer now sets ChangesMap tile referrer policy
Estimated code review effort: 1 (Trivial) | ~2 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to Map tile requests now include an origin referrer under restrictive page policies, restoring default OpenStreetMap tiles for affected deployments. The focused change is ready to merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
OpenStreetMap tiles could be blocked when an app's page-level referrer policy removed the identifying
Refererheader. This sets a referrer policy on raster tile images so the browser sends the app origin to the tile provider. It also covers local HTTP apps requesting the existing HTTPS OpenStreetMap tile URL.Related Issue(s)
Verification/QA
kind/*andbackport*label to this PR for proper release notes groupingChecks run
yarn test MapComponent.test.tsx --runInBandyarn tscSummary by CodeRabbit