Create a SSL version of the example_browserclient so that the example can be run on a remote server with a self signed CA certificate.

[danielwoz]

No description provided.

[tk-1001]

This seems like a useful feature. Just a quick question shouldn't there be some kind of mechanism for creation of self signed certificates or do people should just switch test keys at the end?

[danielwoz]

Good question — didn't have a good answer for a while, but just pushed docs on this in nginx/certs/README.txt.

Keeping the committed test keys as-is for convenience (SSL works out of the box), but added two options for trust:

1. No setup: open https://<host>:8002/ once and click through the browser warning — that exception covers the wss:// connection too, no CA install needed.
2. No warnings at all: use mkcert instead, which gives each machine its own local CA rather than everyone sharing the key committed here.

Open to other ideas if you think there's a better approach here.