feat(fetch-proxy): add X-Forwarded-Port header#11265
Merged
Conversation
Contributor
Preview Build AvailableA preview build has been created for this PR. You can install it using: pnpm install "remix-run/remix#preview/pr-11265&path:packages/remix"This preview build will be updated automatically as you push new commits. |
Contributor
|
The preview branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This keeps
X-Forwarded-Hostaligned with the original requestHostvalue while adding a separateX-Forwarded-Portheader whenxForwardedHeadersis enabled. This follows the shape used bynode-http-proxyand avoids changing existing consumers that expect the port to remain inX-Forwarded-Host.Supersedes #10762.
X-Forwarded-Portfor proxied requests whenxForwardedHeaders: trueX-Forwarded-Hostbehavior by continuing to useurl.host80or443for default HTTP/HTTPS ports