Right now our application is designed to facilitate all communication via websockets after the initial load.
We are trying to figure out a solution to safely pass se
Connecting to a wss://
WebSocket URL rather than ws://
will use the browser's standard TLS/SSL encryption to connect to the server. It's equivalent to HTTPS vs HTTP. If you trust your browser's SSL/TLS implementation then you can trust WebSocket wss://
connections since they use the same engine. You will need to have a signed SSL certificate configured with your websocket server, but that's pretty much required anyways.