Switch fixup from HTTP-by-default to HTTPS-by-default |
||
Issue descriptionFixup prepends "http://" if the user types a URL without a scheme. Now that we're switching to "hide HTTPS schemes by default, show HTTP", I think the time is right to consider changing this to prepend https:// by default; that is, if you want http://, you have to type it explicitly. If we did this, we would also want to change the machinery that re-shows a scheme in the omnibox to only re-show HTTP schemes, not HTTPS ones. This would reduce the shifting of text when editing the omnibox. It's basically the "hide HTTP scheme" changes of years back, except for HTTPS instead now that that's the "new normal". There may be considerations here with how the HUP orders search prefixes; whether we need to add some kind of fallback to HTTP if HTTPS fails hard; and potentially other stuff.
,
Aug 15
emilyschechter, estark: Your thoughts? Seems like the right time to do this but I may not be aware of all of the implications of making this change.
,
Aug 15
Ah, here's one that just occurred to me. There are probably a fair number of sites that respond to https:// URLs but don't redirect to them. (Example: www.latimes.com.) They're probably assuming they will never get a lot of traffic to the https:// URL unless they themselves choose to redirect to it.
,
Sep 7
Also see Issue 451295.
,
Sep 10
#3 Could we do a slow percentage rollout over a period of months, to give sites a slow build-up of traffic to their HTTPS version?
,
Oct 16
|
||
►
Sign in to add a comment |
||
Comment 1 by skare@chromium.org
, Aug 8Components: UI>Security>UrlFormatting
Status: Available (was: Untriaged)