Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 3.6.4 not using hosts file in XP, but IE does

more options

I have a VM that I use as my development LAMP server. I run XP on my desktop with FF 3.6.x. Until an upgrade to FF3.6.4 last night, I could always connect to my VM's https://mypse/ and it worked great. Now after the update, FF says it's unable to connect. If I type https://10.139.68.160/ it works fine. If I load the https://mypse in Internet Explorer it works fine. If I 'ping mypse' from a DOS shell, it of course pings and returns the right IP. I tried to even add an entry to c:\windows\system32\drivers\etc\hosts with "10.139.68.160 mypse" and that had no effect on FF either.

Again, this started AFTER the update to 3.6.4

I have an entry in my c:\windows\system32\drivers\etc\hosts that says:

URL of affected sites

http://mypse/ -- it's an internal development site

I have a VM that I use as my development LAMP server. I run XP on my desktop with FF 3.6.x. Until an upgrade to FF3.6.4 last night, I could always connect to my VM's https://mypse/ and it worked great. Now after the update, FF says it's unable to connect. If I type https://10.139.68.160/ it works fine. If I load the https://mypse in Internet Explorer it works fine. If I 'ping mypse' from a DOS shell, it of course pings and returns the right IP. I tried to even add an entry to c:\windows\system32\drivers\etc\hosts with "10.139.68.160 mypse" and that had no effect on FF either. Again, this started AFTER the update to 3.6.4 I have an entry in my c:\windows\system32\drivers\etc\hosts that says: == URL of affected sites == http://mypse/ -- it's an internal development site

All Replies (5)

more options

This screen shot shows pretty much everything all at once so there is a lot of detail there and proof.

more options

For sanity check, I downloaded the FF3.6.3 from this URL:

http://download.mozilla.org/?product=firefox-3.6.3&os=win&lang=en-US

Installed it and as expected the https://mypse worked like a champ, so there is DEFINITELY something broken in FF 3.6.4 networking.

more options

This same thing is happening with v3.6.6 -- can someone PLEASE fix this CRITICAL bug.

It makes Firefox USELESS for developers if we can't resolve names.

I just don't understand why this would break. Why doesn't Firefox use the DNS that the operating system clearly knows about (ping, IE, hosts, etc.)

THIS WORKED IN 3.6.3 -- YOU BROKE IT IN 3.6.4 and 3.6.6 !!!

more options

Cross reference to actual real bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=575339

how silly of me. I thought this forum was the bug tracker. What a waste of my time to put it in here as it seems it just disappears into the interwebz as clearly not one comment on this CRITICAL regression bug other than what I've researched myself. *sigh*

more options