-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: do not forward the referer #2091
Conversation
This PR will trigger a patch release when merged. |
Codecov Report
@@ Coverage Diff @@
## main #2091 +/- ##
=======================================
Coverage 95.33% 95.34%
=======================================
Files 23 23
Lines 3324 3327 +3
Branches 1 1
=======================================
+ Hits 3169 3172 +3
Misses 155 155
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe it would even be better to rewrite the referrer header to the target host ?
No clue what's best. Not sure if they typically write some logic on the edge to validate the referrers. |
## [14.17.1](v14.17.0...v14.17.1) (2022-11-10) ### Bug Fixes * do not forward the referrer ([#2091](#2091)) ([39eed86](39eed86))
🎉 This PR is included in version 14.17.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fix #2090
The importer proxy forward the referer, which is always a localhost url. Just removing it unblocks the request from #2090. I even wonder why more of customer imported sites did not complain.
PR is also fixing the failing linting introduced by 645fdfa.