Re:Chrome 68 will mark all HTTP sites as “not secure”
by lorenzhs on Friday February 09, 2018 @11:30AM
(#16341516)
I sort of have the reverse problem. I would like to use a websocket to connect to an insecure host on the local network from a secure context. I realise that this is incredibly niche and would probably need independent confirmation through the browser to prevent abuse. But it's needed to connect to a local weechat instance from Glowing Bear, which is essentially a web UI for WeeChat, an IRC client: https://github.com/glowing-bear/glowing-bear. Right now we have an https and a non-https-version of the website, which is arguably even worse.
[ Parent
| on HN ]
There are no comments on this comment yet.