Originally posted here.
This feature entered testing last month, and it rolled out as part of a limited experiment for users of Chrome Canary, Dev, or Beta.
The change will be rolling out to Chrome Desktop and Chrome for Android stable versions after updating to version 90 (to be released on April 13), with an iOS rollout scheduled for later this year.
This move is part of a larger effort to defend users from attackers attempting to intercept their unencrypted web traffic and speed up the loading of websites served over HTTPS.
"Chrome will now default to HTTPS for most typed navigations that don't specify a protocol," Chrome team's Shweta Panditrao and Mustafa Emre Acer said.
"In addition to being a clear security and privacy improvement, this change improves the initial loading speed of sites that support HTTPS, since Chrome will connect directly to the HTTPS endpoint without needing to be redirected from http:// to https://.
"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).
