Skip to content

Conversation

@vietj
Copy link
Member

@vietj vietj commented May 30, 2025

Motivation:

When the HTTP client connection ugprades to a WebSocket it sets a timeout for the WebSocket handshake, when the upgrade is succesfull it cancels the timeout timer.

The current cancellation check does not account for the initial timer ID that is 0.

Changes:

Cancel correctly the timeout timer.

@vietj vietj added this to the 5.0.1 milestone May 30, 2025
@vietj vietj linked an issue May 30, 2025 that may be closed by this pull request
Motivation:

When the HTTP client connection ugprades to a WebSocket it sets a timeout for the WebSocket handshake, when the upgrade is succesfull it cancels the timeout timer.

The current cancellation check does not account for the initial timer ID that is 0.

Changes:

Cancel correctly the timeout timer.
@vietj vietj force-pushed the fix-incorrect-client-web-socket-upgrade-timeout-check-5.0 branch from a31ca5e to cad0556 Compare May 30, 2025 23:07
@vietj vietj merged commit c24eec9 into 5.0 May 30, 2025
7 checks passed
@vietj vietj deleted the fix-incorrect-client-web-socket-upgrade-timeout-check-5.0 branch May 30, 2025 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handshake timeout timer is not cancelled after a successful handshake

2 participants