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

Issue 750414 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ mkwst@chromium.org
est...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome ignores hosts file for localhost

Reported by cukes.i...@gmail.com, Jul 29 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Start up a web application on the host machine (ip: 10.63.240.44) which can be access at http://localhost:9191/vauthtestbed/index.jsp
2. Docker container with /etc/hosts file having two entries <127.0.0.1 localhost> and <10.63.240.44 localhost>.
3. Docker container with no_proxy=*.local, localhost
4. Docker container access http://localhost:9191/vauthtestbed/index.jsp using Chrome, it failed.
5. The same Docker container access the same address using Firefox, it succeeded.

What is the expected behavior?
Chrome is supposed to display the web page as Firefox does.

What went wrong?
Chrome shows ERR_CONNECTION_REFUSED.

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: Ubuntu 16.04 LTS
Flash Version:
chrome_hostname_resolving.jpg
64.3 KB View Download

Comment 1 Deleted

Comment 2 Deleted

Comment 3 by cukes.i...@gmail.com, Jul 29 2017 

What I am trying to achieve is that inside Docker container accessing http://localhost:9191/vauthtestbed/index.jsp which is running on the host machine.

If accessing the web application with ip address, it works. But I want to access with localhost.

Both Chrome and Firefox use system proxy.

Comment 4 by cukes.i...@gmail.com, Jul 30 2017 

Please have a look at the attached screenshots for events, which shows that it does not use proxy [events_1] but the address list [events_2] does not have all mappings for localhost only 127.0.0.1 and ::1.
events_1.JPG
63.5 KB View Download
events_2.JPG
37.3 KB View Download

Comment 5 by mmenke@chromium.org, Jul 31 2017

Cc: mkwst@chromium.org est...@chromium.org
Components: -Internals>Network Internals>Network>DNS
Status: WontFix (was: Unconfirmed)
Summary: Chrome ignores hosts file for localhost (was: Chrome is not able to handle host name resolution in sequence)
"localhost" lookups are magical, and bypass normal name resolution, so this is expected behavior.
►

Sign in to add a comment