-
Notifications
You must be signed in to change notification settings - Fork 234
feat(router): per-message-deflate with context takeover support for websockets #2549
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
Closed
Closed
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
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.
🧩 Analysis chain
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 101
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 43
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 453
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 174
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 1487
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 107
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 182
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 182
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 291
🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 4277
🌐 Web query:
gorilla/websocket v1.5.1 DefaultDialer settings HandshakeTimeout💡 Result:
In gorilla/websocket v1.5.1,
websocket.DefaultDialeris defined with:Proxy: http.ProxyFromEnvironmentHandshakeTimeout: 45 * time.Second(i.e., 45s) [1]Dialer.HandshakeTimeoutonly limits how long the initial WebSocket opening handshake is allowed to take (“duration for the handshake to complete”)—it is not an idle timeout and it does not govern ping/pong intervals after the connection is established [1]. If your connection drops after being idle, that’s typically due to your app’s read deadlines / ping-pong handling or an intermediate proxy/load balancer timeout, notHandshakeTimeout.Sources:
[1] Go package docs (
DefaultDialervalue andHandshakeTimeoutfield doc) https://pkg.go.dev/github.com/gorilla/websocket (showsDefaultDialerwithHandshakeTimeout: 45 * time.Secondand describesHandshakeTimeout)🏁 Script executed:
Repository: wundergraph/cosmo
Length of output: 1480
Preserve DefaultDialer settings when customizing the WebSocket dialer.
The zero-value
websocket.DialerlacksHandshakeTimeout(45 seconds fromwebsocket.DefaultDialer), which means a stalled upgrade handshake will hang indefinitely instead of timing out. The retry loop cannot compensate since there's no per-attempt timeout. Clonewebsocket.DefaultDialerand override only the fields you need:♻️ Suggested fix
func (e *Environment) GraphQLWebsocketDialWithRetry(header http.Header, query url.Values) (*websocket.Conn, *http.Response, error) { - return e.graphQLWebsocketDialWithRetry(websocket.Dialer{ - Subprotocols: []string{"graphql-transport-ws"}, - }, header, query) + dialer := *websocket.DefaultDialer + dialer.Subprotocols = []string{"graphql-transport-ws"} + return e.graphQLWebsocketDialWithRetry(dialer, header, query) } // GraphQLWebsocketDialWithCompressionRetry is like GraphQLWebsocketDialWithRetry but enables // permessage-deflate compression negotiation on the client side. func (e *Environment) GraphQLWebsocketDialWithCompressionRetry(header http.Header, query url.Values) (*websocket.Conn, *http.Response, error) { - return e.graphQLWebsocketDialWithRetry(websocket.Dialer{ - Subprotocols: []string{"graphql-transport-ws"}, - EnableCompression: true, - }, header, query) + dialer := *websocket.DefaultDialer + dialer.Subprotocols = []string{"graphql-transport-ws"} + dialer.EnableCompression = true + return e.graphQLWebsocketDialWithRetry(dialer, header, query) }📝 Committable suggestion
🤖 Prompt for AI Agents