Reputation: 1563
Is there any way to disconnect a client with SocketIO, and literally close the connection? So if someone is connected to my server, and I want to close the connection between them and my server, how would I go about doing that?
Upvotes: 143
Views: 201525
Reputation: 2034
To disconnect socket forcefully from server side
socket.disconnect(true)
OR
To disconnect socket by client side event
On client:
socket.emit('forceDisconnect');
On Server:
socket.on('forceDisconnect', function(){
socket.disconnect(true);
});
Upvotes: 2
Reputation: 3373
I have using the socket client on React Native app, when I called socketIOClient.disconnect()
this disconnects from the server but when I connect to the socket again the previous events were connected again, and the below code works for me by removing all existing events and disconnecting socket conneciton.
socketIOClient.removeAllListeners();
socketIOClient.disconnect(true);
Upvotes: 0
Reputation: 41
You can do socket = undefined
in erase which socket you have connected. So when want to connected do socket(url)
So it will look like this
const socketClient = require('socket.io-client');
let socket;
// Connect to server
socket = socketClient(url)
// When want to disconnect
socket = undefined;
Upvotes: 0
Reputation: 650
Checking this morning it appears it is now:
socket.close()
https://socket.io/docs/client-api/#socket-close
Upvotes: 12
Reputation: 2810
This didn't work for me:
`socket.disconnect()`
This did work for me:
socket.disconnect(true)
Handing over true
will close the underlaying connection to the client and not just the namespace the client is connected to Socket IO Documentation.
An example use case: Client did connect to web socket server with invalid access token (access token handed over to web socket server with connection params). Web socket server notifies the client that it is going to close the connection, because of his invalid access token:
// (1) the server code emits
socket.emit('invalidAccessToken', function(data) {
console.log(data); // (4) server receives 'invalidAccessTokenEmitReceived' from client
socket.disconnect(true); // (5) force disconnect client
});
// (2) the client code listens to event
// client.on('invalidAccessToken', (name, fn) => {
// // (3) the client ack emits to server
// fn('invalidAccessTokenEmitReceived');
// });
Upvotes: 5
Reputation: 5254
Add new socket connections to an array and then when you want to close all - loop through them and disconnect. (server side)
var socketlist = [];
io.sockets.on('connection', function (socket) {
socketlist.push(socket);
//...other code for connection here..
});
//close remote sockets
socketlist.forEach(function(socket) {
socket.disconnect();
});
Upvotes: -2
Reputation: 1741
I am using on the client side socket.disconnect();
client.emit('disconnect') didnt work for me
Upvotes: 0
Reputation: 229
I'm using client.emit('disconnect')
+ client.removeAllListeners()
for connected client for ignore all events after disconnect
Upvotes: 2
Reputation: 11
Socket.io uses the EventEmitter pattern to disconnect/connect/check heartbeats so you could do. Client.emit('disconnect');
Upvotes: 1
Reputation: 858
In my case I wanted to tear down the underlying connection in which case I had to call socket.disconnect(true)
as you can see is needed from the source here
Upvotes: 3
Reputation: 131
Any reason why you can't have the server emit a message to the client that makes it call the disconnect function?
On client:
socket.emit('forceDisconnect');
On Server:
socket.on('forceDisconnect', function(){
socket.disconnect();
});
Upvotes: 12
Reputation: 25645
Edit: This is now possible
You can now simply call socket.disconnect()
on the server side.
My original answer:
This is not possible yet.
If you need it as well, vote/comment on this issue.
Upvotes: 173
Reputation: 1007
For those who found this on google - there is a solution for this right now:
Socket.disconnect()
kicks the client (server-side). No chance for the client to stay connected :)
Upvotes: 5
Reputation: 273
socket.disconnect()
can be used only on the client side, not on the server side.
Client.emit('disconnect')
triggers the disconnection event on the server, but does not effectively disconnect the client. The client is not aware of the disconnection.
So the question remain : how to force a client to disconnect from server side ?
Upvotes: 20