New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 613545 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome can't resolve http://apple.news (https works)

Project Member Reported by pinkerton@chromium.org, May 20 2016

Issue description

Version: m51 beta
OS: iOS, OSX

We discovered an issue where typing/pasting apple.news links into Google Chrome won’t resolve. Note that typing https://apple.news links into Chrome do work — the issue is just when you omit https://.

The problem appears on iOS and OS X. I don’t have a Windows machine to check.

Typing apple.news should redirect you to apple.com/news, but it doesn’t.

Same deal with any article link without https://

https://apple.news/AfY9Sdb97TkizvzJs--IjDg

Looks like Chrome may not have apple.news in a list of valid TLDs, so it sees “apple.news” as a search term not a domain.

 
Cc: pkasting@chromium.org rsleevi@chromium.org
Components: -Internals>Network>DNS UI>Browser>Omnibox
Hrrm, looks like news is is effective_tld_names.dat: https://code.google.com/p/chromium/codesearch#chromium/src/net/base/registry_controlled_domains/effective_tld_names.dat&l=9075

This is more of an omnibox issue than a DNS issue in terms of figuring out if search or naviness. 
Components: -UI>Browser>Omnibox UI>Browser>Navigation
Labels: -Pri-2 Pri-3
Played with it and the issue isn't PSL. 

The issue is that apple.news will do TCP RSTs on port 80, and does not advertise an HSTS header when successfully connecting over port 443. The typical way this is done is a redirect on the http traffic to the https service.

Solving this client-side would mean that we'd automatically have to try https if http fails, or some other heuristic. There may be interest in doing something like this to increase https adoption, but usually the issue is the inverse (the site listens on https but will redirect to http, or even be broken on https).
Cc: eugene...@chromium.org justincohen@chromium.org
Status: WontFix (was: Untriaged)
Based on the analysis in #2, this seems like not a Chrome bug. Safari manifests the same issue: the site just doesn't respond on port 80, and doesn't let us know we should https upgrade. I'm gonna close this as WontFix.
Thanks for taking a look. I've pushed back with the folks who reported the bug. 

Sign in to add a comment