Re: Issue 26545 in chromium: Chrome ignores windows HOSTS file
chro...@googlecode.com
Comment #8 on issue 26545 by jonathancorwin: Chrome ignores windows HOSTS
file
http://code.google.com/p/chromium/issues/detail?id=26545
I also have this problem, so it's not a one-off.
I have overridden hosts in my hosts file and they've been there for a month
and
several reboots, so cant't see it being a caching issue.
Firefox/IE correctly obey the overriden IP addresses and have done since
day one.
Chrome ignores them and uses the DNS.
Windows XP Professional SP3, with a corporate proxy server.
Tried it with DNS prefetching on and off.
Not sure why the ignore list of the proxy settings should make a difference,
shouldn't the hosts file be checked first regardless?
Chrome 4.0.249.78 beta (36714)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
chro...@googlecode.com
Comment #9 on issue 26545 by ero...@chromium.org: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
@jonathoncorwin: If you are sending requests through a proxy server, DNS
resolution
won't come into play, since the DNS resolving will be done by the proxy. If
on the other
hand those domains are on the proxy exclusion list, then the resolves will
be done
client-side (and hence hit the modifications from HOSTS file)...
chro...@googlecode.com
Comment #10 on issue 26545 by s...@bigorno.net: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
Also have this problem w/Chrome 3.0.195.38 on XP Pro SP3
Entries have been in the host file for ages and several reboots.
No proxy configured.
Firefox is OK
IE8 is OK
Chrome is NOT
If I understand correctly Chrome uses the general Windows settings for
proxy, so
should it be a proxy issue, IE too would be impacted.
?
chro...@googlecode.com
Comment #15 on issue 26545 by ero...@chromium.org: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
@keith there shouldn't be anything special in chrome for avoiding 127.0.0.1
addresses.
Can you try loading up chrome://net-internals/#dns and see what the IP
addresses it observed for those hostnames were?
chro...@googlecode.com
Comment #16 on issue 26545 by keith.gr...@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
@eroman: It appears to be a caching issue. Firefox and IE pick up the hosts
file changes immediately, chrome apparently does not, and can sometimes
take up to 20 mins to see changes. This isn't a really big issue, it's just
mildly annoying as Chrome is my preferred browser. Is there a way to force
it to not use the cache when reloading a page? Similar to how shift+refresh
works in Firefox?
chro...@googlecode.com
Comment #17 on issue 26545 by ero...@chromium.org: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
@keith: 20 minutes? That is not likely Chrome's DNS cache, since Chrome's
DNS cache expires after 1 minute.
Can you follow the instructions on about:net-internals to get a text dump?
Also if you are investigating on your end you can check out
about:net-internals/#dns to see what DNS chrome is caching.
chro...@googlecode.com
Comment #18 on issue 26545 by drewni...@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
I'm experiencing this issue in Chrome 12.0.742.112, Windows Vista, 32 bit.
No proxy. Changes to the Windows hosts file are immediately accepted by IE
and Firefox, but Chrome does not respect the changes until the browser is
restarted, or 20 to 30 minutes pass.
chro...@googlecode.com
Comment #23 on issue 26545 by bhaskar....@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
Is there a Linux equivalent of this bug? I am facing the same issue.
Using Chrome build 16.0.912.63 on Ubuntu.
Hosts file maps "facebook.com" to "1.2.3.4". Both ping and firefox obey the
directive. But chome connects to the DNS and successfully resolves
facebook.com. AFAIK I am not behind any proxy server. Also it depends on
who does the dns resolution in case it is a forward proxy or a transparent
proxy, there is a difference. Please fix this issue. Thanks.
chro...@googlecode.com
Comment #27 on issue 26545 by kalyan.g...@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
Even i am seeing same issue with Chrome 18.0.1025.165 on Mac.
chro...@googlecode.com
Comment #28 on issue 26545 by fen.laba...@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
Why "won't fix"? I build web sites and create local versions with
non-standard DNS entries like example.6 (for an example.com site running on
Drupal 6) using entries in /etc/hosts. The problem is not that /etc/hosts
is not consulted (I can ghost example.com with /etc/hosts) but rather seems
to be that the domain name is not properly constructed. I have seen this
on Mac OSX and Linux (currently on Ubuntu 12.04 and Chrome 18.0.1025.151).
I (and my colleagues) do this regularly and are forced to use Firefox,
Safari or other browsers because Chrome can't resolve these non-standard
names.
chro...@googlecode.com
Comment #29 on issue 26545 by Ricochet...@gmail.com: Chrome ignores windows
HOSTS file
http://code.google.com/p/chromium/issues/detail?id=26545
I have this same issue on Linux (Kubuntu 12.04) with Chromium.
I have No Proxy set! Please don't ignore this issue or say it is not an
issue.
I do web development and have a local webserver I use for testing. To test
the web app and make it think that it is at the actual domain, I modify the
/etc/hosts file. Usually it works, but recently this has stopped working
in Chromium. Instead, Chromium consistently bypasses/ignores /etc/hosts
and looks up the address via DNS, resulting in an inability to reach the
local webserver. Other browsers read /etc/hosts and follow it.