We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Transport does not get updated when upgrade from WebSocket to WebTransport (when manually disable polling).
polling
To Reproduce
Please fill the following code example:
Engine.IO server version: 6.6.4
6.6.4
Server
(Omitted, a correctly configured socket server with WebTransport enabled, see https://github.com/socketio/socket.io/blob/main/examples/webtransport/index.js)
Engine.IO client version: 6.6.3
6.6.3
Client
<!doctype html> <html> <head> <meta charset="UTF-8"> <title>Socket.IO WebTransport example</title> </head> <body> <script src="engine.io.js"></script> <script> const socket = new eio({ transports: ['websocket', 'webtransport'], transportOptions: { websocket: { port: 1500 }, webtransport: { port: 1650 }, }, }); </script> </body> </html>
Expected behavior Subsequent request should sent by WebTransport.
Actual behavior
engine.transport is still a WebSocket, marked upgrading = true, make it never success to sendmessage for both transports.
engine.transport
upgrading = true
Additional context
In following code snippet, the callback in pause() would not be called if the original transport is WebSocket.
pause()
socket.io/packages/engine.io-client/lib/socket.ts
Lines 1029 to 1042 in e95f6ab
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Transport does not get updated when upgrade from WebSocket to WebTransport (when manually disable
polling
).To Reproduce
Please fill the following code example:
Engine.IO server version:
6.6.4
Server
(Omitted, a correctly configured socket server with WebTransport enabled, see https://github.com/socketio/socket.io/blob/main/examples/webtransport/index.js)
Engine.IO client version:
6.6.3
Client
Expected behavior
Subsequent request should sent by WebTransport.
Actual behavior

engine.transport
is still a WebSocket, markedupgrading = true
, make it never success to sendmessage for both transports.Additional context
In following code snippet, the callback in
pause()
would not be called if the original transport is WebSocket.socket.io/packages/engine.io-client/lib/socket.ts
Lines 1029 to 1042 in e95f6ab
The text was updated successfully, but these errors were encountered: