Secure Websocket support

[D4nte]

We currently use a go-waku instance as a gateway to the waku test fleet in the js-waku web app.

After further investigation, we can confirm that, regarding the support of insecure websocket ws in a secure web page https:
- Firefox supports it only if some advance security parameters are modified using about:config.
- Chrome does not support it at all.

This means that js-waku must support wss to be relevant.

Also, go-waku being able to listen on a secure websocket wss would allow a smooth experience for web app demo and also testing of wss (as nim-waku does not yet support websockets).

@richard-ramos can you please consider adding support?

[richard-ramos]

Since there's no support out of the box for listening / dialing wss multiaddresses (see: libp2p/go-ws-transport#70), I setup a reverse proxy with nginx that uses a self signed certificate to add secure websockets support.

To test, you can use /ip4/134.209.113.86/tcp/443/wss/p2p/16Uiu2HAmVVi6Q4j7MAKVibquW8aA27UNrA4Q8Wkz9EetGViu8ZF1

[richard-ramos]

The config used for nginx in my DO droplet can be seen here: https://gist.github.com/richard-ramos/63eadded212aaa994216f98583acc257

[richard-ramos]

Closing this issue, as WSS listening support can be achieved with nginx, and dialing WSS nodes is not required at the moment.