I’m unsure weather it works. But here’s my idea/suggestion: Idea: I assume that you (possibly) tried to access a URL which is too long. This happens if data often is tansmitted via GET-Parameters. The official limit for a URL is below 512 Bytes. Details: The HTTP specification says that a protocol line may be at … Read more
Redis pub/sub is great in case all clients have direct access to redis. If you have multiple node servers, one can push a message to the others. But if you also have clients in the browser, you need something else to push data from a server to a client, and in this case, socket.io is … Read more
Put your on disconnect code inside your on connect block and edit it a bit like so: io.sockets.on(‘connection’, function (socket) { count++; io.sockets.emit(‘count’, { number: count }); socket.on(‘disconnect’, function () { console.log(‘DISCONNESSO!!! ‘); count–; io.sockets.emit(‘count’, { number: count }); }); }); This way you’re detecting when a specific socket (specifically the socket you pass to … Read more
I think what we need to understand in order to answer this question is how exactly the underlying TCP connection evolves during the whole WebSocket creation process. You will realize that the sticky part of a WebSocket connection is the underlying TCP connection itself. I am not sure what you mean with “session” in the … Read more
I have found a solution. for some reason the default transportation method is not always allowed by all servers. So i specified a neutral transportation method at the client side, like this: var socket = io(‘https://yourDomain:3000’, { transports : [‘websocket’] });
Make sure that both client and server have same major version of socket.io. For example, combination of socket.io@2.3.0 on server and socket.io-client@3.x.x at client leads to this case and the ‘connect’ event is not dispatched.
There are similar questions that will help you with this: Socket.IO – how do I get a list of connected sockets/clients? Create a list of Connected Clients using socket.io My advice is to keep track yourself of the list of connected clients, because you never know when the internal API of Socket.IO may change. So … Read more
A heartbeat is a small message sent from a client to a server (or from a server to a client and back to the server) at periodic intervals to confirm that the client is still around and active. For example, if you have a Node.js app serving a chat room, and a user doesn’t say … Read more
Using Socket.IO 0.8.7, you can access request headers via: socket.handshake.headers You can find more detail on this at https://github.com/LearnBoost/socket.io/wiki/Authorizing
Some mobile phone operators are notoriously known for setting up utterly broken transparent proxies that you’re forced to pass through. This is a real annoyance that the WebSocket working group has had to deal with since the very beginning. The protocol is designed to ensure that it will fail very quickly in presence of such … Read more