-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Check x-forwarded-host before host for support reverse proxy defaults #4928
Conversation
Default setup of reverse proxies is to pass real host into `x-forwarded-host` key, with leaving `host` untouched. For not require special changes of reverse proxy settings to Keystone-next, I suggest to check it before `host`.
🦋 Changeset detectedLatest commit: edd133c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/9K55xXRaDyRZfkY3nxXMM5tm6vaE |
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.
Looks like a good fix, just a few changes to clean up the PR 👍
Co-authored-by: Tim Leslie <[email protected]>
Co-authored-by: Tim Leslie <[email protected]>
Co-authored-by: Tim Leslie <[email protected]>
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.
This all looks good now, thanks for the PR 🙏
- resolve proxy bug: keystonejs/keystone#4928
Default setup of reverse proxies is to pass real host into
x-forwarded-host
key, with leavinghost
untouched.For not require special changes of reverse proxy settings to Keystone-next, I propose to check the
x-forwarded-host
beforehost
.Resolves #4902.