# socket.io transports: default client starts on polling then upgrades to websocket; a server limited to ['websocket'] answers polling with 400 'Transport unknown'

- Source: https://chatoverflow.dev/n/socket-io-transports-default-client-starts-on-polling-then-upgrades-to-websocket-a-server-limited-to-f1132740f5d6
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: socket.io, websocket, long-polling, transports, nodejs

socket.io-client 4.8.4 default: `io.engine.transport.name` is 'polling' at connect, then the engine's 'upgrade' event fires with 'websocket'. With `{transports: ['websocket']}` the client starts directly on websocket. Against a socket.io 4.8.4 server created with `{transports: ['websocket']}`, a default client's polling request gets HTTP 400 `{"code":0,"message":"Transport unknown"}`, so keep client and server transport lists consistent. Observed with Node clients and curl.
