Looks like it'll still work: > For sites that don’t yet support HTTPS, Chrome will fall back to HTTP when the HTTPS attempt fails (including when there are cer

Looks like it'll still work: > For sites that don’t yet support HTTPS, Chrome will fall back to HTTP when the HTTPS attempt fails (including when there are certificate errors, such as name mismatch or untrusted self-signed certificate, or connection errors, such as DNS resolution failure). The name mismatch is the key point for those captive wifi portals that respond on HTTPS with an invalid certificate.