Socket.IO v3 transport ordering change obscures fallback diagnosis in debug logs
Context Socket.IO v3 reversed the default client transport priority to ["websocket", "polling"] , making WebSocket the first attempt and only falling back to long-polling after a handshake failure. When corporate proxies block the WebSocket upgrade, the client enters a reconnect loop that emits repeated socket.io:transport debug entries. Problem No dedicated
socketio