feat: ws connection support https redirects before upgrade - #66
Open
hsxfjames wants to merge 1 commit into
Open
Conversation
Signed-off-by: Eugene Zheng <hsxfjames@gmail.com>
hsxfjames
force-pushed
the
feat/support-ws-redirects
branch
from
August 10, 2026 08:41
25ad765 to
a755505
Compare
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
1 participant
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.
Background
When the EZM WebSocket service is deployed behind a gateway that enforces HTTP-to-HTTPS redirects, a client configured with
ws://example.com/wsshould follow this connection flow:301or302redirect to the HTTPS endpoint.101 Switching Protocols, establishing a secure WebSocket connection.By default, the Node.js
wsclient does not follow HTTP redirects. As a result, the connection fails when the gateway returns the initial redirect response.Changes
This PR enables redirect handling by setting
followRedirectstotrueand limits the redirect chain to a maximum of 3 redirects.This allows WebSocket connections to work in deployment environments where HTTPS is enforced by an upstream gateway, while preventing unbounded redirect chains.