lzh/websockify
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
adding WSS exceptions for dummies
This commit is contained in:
don bright
2023-01-07 16:34:17 -06:00
committed by GitHub
parent d54020538d
commit 7f53e9c22c
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -1
View File
@@ -55,7 +55,13 @@ understand it. You can do this by installing it as accepted certificate, or by
using that same certificate for a HTTPS connection to which you navigate first using that same certificate for a HTTPS connection to which you navigate first
and approve. Browsers generally don't give you the "trust certificate?" prompt 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