Copying socket.io.js to a public folder (something as resources/js/socket.io.js) is not the proper way to do it. If Socket.io server listens properly to your HTTP server, it will automatically serve the client file to via http://localhost:<port>/socket.io/socket.io.js, you don’t need to find it or copy in a publicly accessible folder as resources/js/socket.io.js & serve it manually. … Read more
Did you try: socket.disconnect() on client?
Seems I was able to solve this for myself after opening a bounty. Sorry about that. Anyway, see if this helps: chat.on(‘connection’, function (socket) { socket.on(‘message’, function (msg) { socket.emit(msg); // Send message to sender socket.broadcast.emit(msg); // Send message to everyone BUT sender }); }); However, you could save some bandwidth and create a more … Read more
There is a lot of common misinformation in this thread that is very inaccurate. TL/DR; WebSocket replaces HTTP for applications! It was designed by Google with the help of Microsoft and many other leading companies. All browsers support it. There are no cons. SocketIO is built on top of the WebSocket protocol (RFC 6455). It … Read more
There are two types of “upgrades” happening with socket.io. First (in socket.io 1.0+), socket.io starts all connections with an http polling request and it may actually exchange some initial data with just an http request. Then, at some point after that, it will try to actually initiate a webSocket connection. the webSocket connection is done … Read more
If you’re running Express 4, it appears to me like you’re missing the lines of code: var app = express(); var server = app.listen(3000); That will start your web server and set it to port 3000. See the bone simple Express 4 app here: http://expressjs.com/4x/api.html And, then to start up socket.io, you would add: var … Read more
Here is a solution using Socket.IO 1.0 and Express 4.0. It is similar in spirit to Patrick’s answer. The trick is that since Socket.IO 1.0 has a new middleware API, we can wrap Express’s middleware and put it into the Socket.IO pipeline without delving into the low-level implementation of the session stores. // Set up … Read more
When the server closes the connection, the client does not try to reconnect. With some JS frameworks maybe, but the question was, at the time of this answer, tagged as plain Vanilla JS. I’m a bit frustrated because the accepted, upvoted answer is plainly wrong, and it cost me some additional time while finding the … Read more
Non-privileged user (not root) can’t open a listening socket on ports below 1024. Check this Give Safe User Permission To Use Port 80 Remember, we do NOT want to run your applications as the root user, but there is a hitch: your safe user does not have permission to use the default HTTP port (80). … Read more
Just in case someone gets to this page while using socket.io version 1.0 You can get the connected clients count from socketIO.engine.clientsCount Need an answer and the above did not work for new version of socket.io