You can clone with
HTTPS or Subversion.
In the open issues in the readme you state: "Haven't tested TLS for the Server. (Perhaps this is handled automatically by attaching the WebSocket server to a https.createServer instead of http.createServer?) My server implements TLS via stunnel->haproxy->node."
I can confirm it works out of the box.
In the server example script I created a https server and at the client side I call "wss://".
Fantastic! I'll update the README. Thanks!
in the echo-server.js (under test/), i did what pors mentioned in the above post, creating https server on the server side and replacing w/ wss on the client, but it still didn't work for me. could you please help out?
Note that your client must have the certificate accepted. If you have the https setup you can browse to that manually and then you will get the 'accept cert' message, after which you will be able to connect.
Yes, I confirm James. I have a https setup and wss server. When I try connect to wss server from https web page, I can not connect from Firefox. I must manually request wss connection first, then firefox warn for certificate, When I accept certificate, later it works normally. However Firefox does not warn or load wss certificate automatically.
I also test with Chrome and it works normally. (It automatically load wss certificate without manually pointing it)
Safari behaves same as Firefox.
If we think about browser's security chain, it should be fine asking user about certificate acceptance if there is another ssl request from https web page loaded. But it does not even ask. That seems problem.
Although system works normally after manually force requesting wss certificate, this is not useful for common users. Do someone has an idea how to solve it?