Add .localhost to the list of TLD
Reported by
johannes...@gmail.com,
Oct 18 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Setup a local web server, configure host to resolve for instance demo.localhost addresses to 127.0.0.1 2. on the web server Set up (virtual) hosts-domains for instance demo.localhost 3. in chrome navigate to demo.localhost What is the expected behavior? Open the locally served content What went wrong? chrome starts a web search Did this work before? No Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: n/a OS Version: 10.0 Flash Version: Make the list of TLD configurable will make it easier to test different TLDs
,
Oct 18 2017
Cool. How do I add a TLD to the list of known TLDs that chrome will not attempt a search?
,
Oct 18 2017
I do not think you can. And I would not count on having such an option. The TLD list is very large and it is probably converted into a highly optimized binary format for quick-in-memory-access. Making it customizable will probably slow down the network stack, URL resolution and cookie mechanism (among others) significantly.
,
Oct 19 2017
,
Oct 19 2017
,
Oct 19 2017
.localhost is not a true TLD, and should not be in the master TLD list. The omnibox should prompt "did you mean to navigate" if you "search" for an intranet hostname that is successfully navigable, and remember such navigations in the future. Fixing bug 104638 would expand this so that a successful navigation to any .localhost address would make all future entries ending in ".localhost" navigate by default. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phistuck@gmail.com
, Oct 18 2017