3 ms·
This is a great instance of https://xkcd.com/1172/ https://xkcd.com/1172/ for me. "example.com" is the only domain name I intentionally load over HTTP in Chrome
by goodside 6y ago
This is a great instance of https://xkcd.com/1172/ https://xkcd.com/1172/ for me. "example.com" is the only domain name I intentionally load over HTTP in Chrome, so this change breaks my workflow.
Many for-pay wifi networks (e.g. on airplanes) are designed to intercept all HTTP requests from guest users, redirecting the browser to a login/signup page. Until you log in HTTPS is blocked, so you have to try to open a domain Chrome doesn't recognize as requiring HTTPS. There are fewer of these every year, so I use "example.com" because it autocompletes easily and will be around forever. Now there's no domain that works, and you have to type every character of "http://a http://a" to get the same result.
- louis-lau 6y agoDid you read the blog post? It will now use http if https fails. So http only sites will still work for this.
- CGamesPlay 6y agoHey, take a look over the HN guidelines, specifically this one: > Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- goodside 6y agoThat's not the issue. Example.com is just distinctive for supporting both http and https, whereas modern sites redirect you to the https version. Chrome remembers which domains support https (which is nearly all of them) for when the domain is typed naked, and apparently won't fall back to http if it recalls https working in the past. So, until now, domains like "example.com" would sometimes let you get to an airplane's login page when domains like "facebook.com" wouldn't.
- CGamesPlay 6y agoYou're gonna want to switch to http://neverssl.com http://neverssl.com, with is designed precisely for this purpose. The new Chrome behavior will not break this site.