with node > 7
npm install sack.vfs
node testWssHttps.js
opens a server on port 8080, and 8081
should replace /*should be valid IP*/
in testWssHttps.js with a valid IP that it will be serving... (not localhost or 127.0.0.1)
Connect to https://<server IP>:8080/
This loads the index.html shown above, which connects back to two wss connections.
These connections show up in 'unknown/canceled' but cannot get the certificates from them
The connection to the second results in net::ERR_CERT_AUTHORITY_INVALID
instead of like ERR_CERT_NAME_BAD,
because the cert on the second connection has '127.0.0.1' as the cert name. Which is why the other IP
needs to be set to an IP to serve on and connect to....
the TLS interface exposed through sack.vfs is just a thing wrapper on OpenSSL linked to node.
the network and disk is custom code; it tries to stick to its own directory by referencing '.' prepended to the URL; but this is just a test, and not meant to be fully featured.