Update README.md
adding WSS exceptions for dummies
This commit is contained in:
@@ -57,6 +57,12 @@ and approve. Browsers generally don't give you the "trust certificate?" prompt
|
|||||||
by opening a WSS socket with invalid certificate, hence you need to have it
|
by opening a WSS socket with invalid certificate, hence you need to have it
|
||||||
accept it by either of those two methods.
|
accept it by either of those two methods.
|
||||||
|
|
||||||
|
The ports may be considered as distinguishing connections by the browser,
|
||||||
|
for example, if your website url is https://my.local:8443 and your WebSocket
|
||||||
|
url is wss://my.local:8001, first browse to https://my.local:8001, add the
|
||||||
|
exception, then browse to https://my.local:8443 and add another exception.
|
||||||
|
Then an html page served over :8443 will be able to open WSS to :8001
|
||||||
|
|
||||||
If you have a commercial/valid SSL certificate with one or more intermediate
|
If you have a commercial/valid SSL certificate with one or more intermediate
|
||||||
certificates, concat them into one file, server certificate first, then the
|
certificates, concat them into one file, server certificate first, then the
|
||||||
intermediate(s) from the CA, etc. Point to this file with the `--cert` option
|
intermediate(s) from the CA, etc. Point to this file with the `--cert` option
|
||||||
|
|||||||
Reference in New Issue
Block a user