Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Socket.IO default communication

Mark_d_10
Beginner
104 Views

Hello,

I've noticed that the WebRTC JavaScript client SDK is using Socket.IO for communication to the server and the transport option is set to the default of "polling" and "websocket".
This will make the initial connection to the server using polling requests and exposes the user's session ID in the URL of those requests.
(https://webrtc.example.com/socket.io/?EIO=3&transport=polling&sid=<session_token>)
Is there an option to force the SDK to only use Websockets? If not, can this be added?

Kind Regards,

Mark

0 Kudos
2 Replies
Jianjun_Z_Intel
Employee
104 Views

Hi Mark,

Current, there is no such an option in conference mode. For P2P mode, you can modify sc.websocket.js to force your web app to use WebSocket only.

Mark_d_10
Beginner
104 Views

Hi,

Currently we have done that, but when there will be an update of the library we need to modify again.

So if it can be made configurable in a future release, that would be very nice?

Reply