Omnibox preferring searches over short hostnames |
||||||
Issue description
Chrome Version : 54.0.2840.50
OS Version: Ubuntu 14.04.1 LTS 201609TD4
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Visit a hostname by name who's FQDN is in your /etc/resolv.conf search list, i.e. go/something where go.example.com is the hostname, and example.com is in your /etc/resolve.conf
2. Be taken to google.com search result instead of being sent to http://go/something
What is the expected result?
I expect to be taken to the website.
What happens instead of that?
A google search is performed.
Please provide any additional information below. Attach a screenshot if
possible.
"go/" will take me to the expected site.
"go/something/" will take me to http://go.example.com/something/ but that is an incomplete workaround as not all destinations are happy with a trailing slash.
https://go/ connects, but the webserver there doesn't have a cert signed for the short name, so it throws up a "Your connection is not private" as I would expect (only mentioning it in the event this is some sort of https-first host probing logic bug).
Repeated attempts to visit "go/something" take me to google.com. All without the "Do you want to visit http://go", so it can't be as simple as a slow DNS lookup race.
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.50 Safari/537.36
,
Oct 8 2016
,
Oct 10 2016
Able to reproduce the issue in Windows 10,Mac 10.11.6, Linux Ubuntu 14.04 -Chrome stable version-53.0.2785.143. Manual Bisect: Good build:53.0.2766.0 Bad build:53.0 2767.0 Bisect Tool info: CL: https://chromium.googlesource.com/chromium/src/+log/21281076a0aa41af8a0489964f51f8e952a15a16..5bcbf89d9ccff7e123c0b195e26f0901b7e65eff Possible suspect: https://chromium.googlesource.com/chromium/src/+/5d3592ad6fef8cde3aa0e1a776cb73b7a10bfb43 mpearson@ Please help us to find a right owner if this issue is not related to you.
,
Oct 10 2016
Lacking the "Did you mean to navigate" prompt on the erroneous search pages is probably bug 247848 . Reporter, please try the following: * Shut down Chrome * Ensure all Chrome processes have exited * Restart Chrome, paying particular attention to whether any "your profile could not be opened" sort of messages appear * Check whether go/something will now navigate as expected If any messages about profile errors appear, or navigation still doesn't work, let me know. Otherwise, this is another (worrisome) dupe of the many other such reports about this that seem to resolve themselves after a restart...
,
Oct 11 2016
Finally took a moment to shut down chrome. $ ps auxwwwww | grep --color=auto chrome wathiede 461 0.0 0.0 23756 936 pts/47 S+ 11:16 0:00 grep --color=auto chrome Started up chrome again, no error messages about profile problems as a pop up, nothing in stderr, and the profile badge in the upper right of my window has no yellow/organge 'attention triangle' telling me something is wrong with my account. At first, short hostnames were still taking me to search. However, as I've been typing this, chrome has been busy in the background doing whatever it does, and now go/something is working.
,
Oct 11 2016
Hmmm. I'm worried about this issue. If this happens to you again, please comment here. Until then, closing, since I have no idea how to track this down further (problems that disappear after restarting mean sending me the profile won't help).
,
Oct 11 2016
creis@ was able to repro this and jmukthavaram@ was able to successfully bisect, doesn't that imply you can debug on a fresh install/upgrade? It also means all people upgrading to build:53.0 2767.0 will be bitten by this until they restart chrome (which many high tab count users seldom do).
,
Oct 11 2016
I don't know what steps comment 1 and 3 are taking to reproduce and bisect. It's not enough to just say "go/something doesn't navigate by default but go/ does"; that's expected behavior until you do a typed navigation to go/ or a path within it. Folks in those comments, can you be more specific about exactly how you're testing this? I also don't think this is hitting anywhere near everyone who upgrades, although it's hit more than one person. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by creis@chromium.org
, Oct 7 2016Components: UI>Browser>Omnibox
Labels: -Type-Bug -Pri-3 M-55 M-54 Needs-Bisect OS-Windows Pri-1 Type-Bug-Regression
Owner: pkasting@chromium.org
Status: Untriaged (was: Unconfirmed)