Re:NeverSSL
by _bxg1 on Saturday November 02, 2019 @07:29PM
(#21430863)
Thanks for the explanation - I've definitely encountered that situation. Do you know why it works that way?
[ Parent
| on HN ]
Re:NeverSSL
by manigandham on Saturday November 02, 2019 @07:40PM
(#21430893)
Captive portals require intercepting and redirecting your HTTP request. You can't do that with HTTPS because it's encrypted. Most sites now automatically redirect to HTTPS and are cached that way by browsers so it's hard to find a HTTP-only site that will get redirected on these networks.
Re:NeverSSL
by MrStonedOne on Saturday November 02, 2019 @08:35PM
(#21431172)
Websites can tell browsers to never connect to them via unsecured channels (hsts/hsts preload), in a secured channel the browser validates the server's encryption certificate is authorized to encrypt traffic for that domain, so the wifi network can not intercept it to serve up the captive porter.