-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: preserve HTTPS/HTTP2 host port in @cloudflare/vite-plugin requests #14933
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
Open
intrdx
wants to merge
2
commits into
cloudflare:main
Choose a base branch
from
intrdx:fix/vite-plugin-https-http2-host-port
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+52
−2
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@cloudflare/vite-plugin": patch | ||
| --- | ||
|
|
||
| Preserve the host and non-default port (e.g. `localhost:5173`) when the Vite dev server runs over HTTPS/HTTP2, so authentication flows such as Clerk no longer redirect-loop to the wrong origin |
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
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
Oops, something went wrong.
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.
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.
🟡 New host-resolution behaviour ships without any automated test
The new host/port resolution logic is added (
createRequestcall atpackages/vite-plugin-cloudflare/src/utils.ts:111-118) with no accompanying unit test, even though the package already has a request-handler test harness that could exercise it, so the fix can silently regress.Impact: The port-preserving behaviour could break again in a future change without anyone noticing.
Repository rule and existing test harness make a test feasible
CONTRIBUTING.mdstates "Every PR should include tests for the functionality that's being added". The PR marks "Automated tests not possible", butpackages/vite-plugin-cloudflare/src/__tests__/utils.spec.ts:102-142already sets up a real Node HTTP server and invokescreateRequestHandlerdirectly with a castreq, capturingrequest.url. A test can therefore assert host/port resolution by invoking the returned handler with areqwhoseheaderscontain only:authority(nohost), verifying the captured URL keeps the non-default port and thatX-Forwarded-Hostis populated.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.
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 seems correct. Why are we setting the
Hostheader again when we're already passing in...(host ? { host } : {}),tocreateRequest@intrdx ?