feat!: proxy bypass with WebSocket #18070
Merged
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.
Description
#13218 made Vite's internal WebSocket connection to be able to be proxyed to other servers. But that made it impossible to proxy WebSocket connections while not proxying the internal WebSocket connection (See the table below).
/
/aaa
/
/aaa
This PR makes
proxyOptions.bypass
to be called for WebSocket connections and make that possible.An alternative is to change the WebSocket protocol to
vite-hmr-${randomid}
instead ofvite-hmr
and proxy all WS connections except connections withvite-hmr-${randomid}
. Proxying other Vite server's WS connection is possible because other Vite server would have a differentrandomid
.fixes #17973