344393 - Will not resolve localhost when "No Proxy for:localhost" is used.

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Bob Vincent]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.3 (like Gecko) (Debian)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060406 Firefox/1.5.0.4 (Debian-1.5.dfsg+1.5.0.4-1)

I am running squid as a local proxy server.

With

  Preferences:General:Connection:No Proxy for:localhost

After performing a routine apt-get update (which upgraded firefox to version 1.5.0.4), I tried to access the local CUPS administration page.

Browsing to http://localhost:631/ fails.
Browsing to http://127.0.0.1:631/ succeeds.

Local DNS resolves both localhost and localhost.anydomain.com to 127.0.0.1.

Removing "localhost" from the "No Proxy for:" list solves the problem.

Removing the proxy completely (Direct connection to the internet) also solves the problem.

Using "127.0.0.1" instead of "localhost" solves the problem.

Reproducible: Always

Steps to Reproduce:
1. Install locally-running squid proxy (on 127.0.0.1)

2. Configure Firefox proxy settings as follows:
   (*) Manual proxy configuration:
   HTTP Proxy: 127.0.0.1
   Port: 3128
   No Proxy for: localhost,127.0.0.1

3. Go to http://localhost:631/

4. Go to http://127.0.0.1:631/

5. Clear the "No Proxy for:" list, then
   go to http://localhost:631/ again.

6. Select (*) Direct connection to internet, then
   go to http://localhost:631/ again.
Actual Results:  
3a. With keywords turned on, performs a Google "I'm feeling lucky" search on "localhost".

3b. With keywords turned off but autocomplete turned on, reports "can't find server at www.localhost.com".

3c. With both keywords and autocomplete turned off, reports "can't find server at localhost"

4. Shows CUPS administration page.

5. Shows CUPS administration page.

6. Shows CUPS administration page.

Expected Results:  
Step 3 should have shown the CUPS administration page just steps 4, 5, and 6 did.

/etc/hosts file contains the following line:

127.0.0.1 localhost.razor.html.com localhost.html.com localhost

I am running a local dnscache/tinydns resolver on 10.10.0.30.

/etc/resolv.conf contains:

  search html.com
  nameserver 10.10.0.30

All of the following network tests report an IP address of 127.0.0.1:

ping localhost
dnsqr a localhost.
dnsqr a localhost
dnsqr a localhost.html.com
dnsqr a localhost.razor.html.com

I don't have dig or nslookup installed.

Comment 1

[Bob Vincent]

Just download the latest nightly and confirmed that it has the same problem.

(Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060609 Minefield/3.0a1)

In fact, it's even worse, because it won't connect to http://localhost:631/ even with "Direct connection to internet" (step 6 in original problem report.)

I believe this qualifies as a regression in previously correct behavior, so I am nominating this bug as "Blocking for 2.0"

Comment 2

[Mike Connor [:mconnor]]

Can you tell us when this actually changed behaviour?

Comment 3

[Mike Connor [:mconnor]]

please renominate if you can find a version of Mozilla that does not do this.

Comment 4

[Matthias Versen [:Matti]]

Reporter: Is this still an issue ?

Comment 5

[Bob Vincent]

Dunno -- I'm no longer using squid, but I just fired up the Debian/Testing version of Iceweasel and browsed to http://localhost:631/ and got the CUPS page.  So the regression has been fixed, at least.

Comment 6

[Matthias Versen [:Matti]]

Thanks for your response after this long time !

Comment 7

[Bob Vincent]

Fifteen hours is a long time?

Comment 8

[Bob Vincent]

Sorry, 27 hours. But still...

Comment 9

[Matthias Versen [:Matti]]

I meant that your reported this bug 6 years ago

Comment 10

[Bob Vincent]

And stopped using Firefox for this and other reasons.