198931 - Proxy: problems w/ squid

Status: VERIFIED EXPIRED

(Core :: Networking, defect)

Description

[gustavo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

Mozilla sometimes resolves www.google.com wrong. For example, today
www.google.com leads me to http://www.jptl.co.pt. However:

[gustavo@lifebook gustavo]$ host www.google.com
www.google.com has address 216.239.39.99
[gustavo@lifebook gustavo]$ host www.jptl.co.pt
www.jptl.co.pt has address 213.228.151.3
[gustavo@lifebook gustavo]$

On the other hand www.google.pt works fine although:
[gustavo@lifebook gustavo]$ host www.google.pt
www.google.pt is an alias for www.google.com.
www.google.com has address 216.239.39.99

Note that telnet www.google.com 80 and get www.google.pt 80 give exactly the
same result, as expected.



Reproducible: Sometimes

Steps to Reproduce:
1.go to www.google.com
2.check if you get the right page
3.

Actual Results:  
As I explained in details.

Expected Results:  
Should have lead me to the right www.google.com

Comment 1

[Matthias Versen [:Matti]]

-> networking

Comment 2

[Matthias Versen [:Matti]]

Mozilla use the OS function getbyhostname().
Do you use a proxy ?

Comment 3

[gustavo]

Yes, I use a proxy. It could be that. I'll check it next time it happens.
(something must broke, I don't think google ever was 213.228.151.3)

Comment 4

[Matthias Versen [:Matti]]

which Proxy Do you use ?

Comment 5

[gustavo]

I use squid, with mostly the original configuration.

squid-2.4.STABLE7-1.1mdk

Comment 6

[Matthias Versen [:Matti]]

Can you please do this if you get this again :
a) check with another browser
b) toggle the offline/online button in mozilla's status bar if a) works

Comment 7

[gustavo]

I tried both a) and b). Other browsers worked fine with no proxy configured.
Toggling the online/offline button didn't make any difference.

I'll try other browsers with the proxy next time.

Comment 8

[gustavo]

I confirm the problem to happen on moz 1.1 and 1.2.1, also without proxy usage
and  even after clearing the caches (memory and disk) and using the
online/offline button.

www.google.com was resolved into a wrong page, which I could not get the real
url or ip of.

It resolves ok with other browsers and with the host command

Comment 9

[gustavo]

I sware this is not a joe ;-)

http://cloudy.daemon.sh/~gustavo/google.png

Comment 10

[Matthias Versen [:Matti]]

Reporter: Is this still a problem in recent builds ?

Comment 11

[gustavo]

I continued to use mozilla 1.1 and this problem didn't happen again. Perhaps it
happens very rarely. I upgraded to FireBird 0.6 today, and will let you know in
case the problem comes up.

As I said, it happened only a couple of times with mozilla 1.1, so this might
not be obvious.

Comment 12

[Jens Prüfer]

Attachment: screenshot after googlification of firefox 0.8

After a google search, all open websites only link to google host, no matter
which link you click until proxy connection is disabled and direct connection
is used instead.

Comment 13

[Jens Prüfer]

*sigh* all my additions collided in mid air, so here I go again ...

I can confirm the bug for firefox 0.8/german edition on Linux using junkbuster
proxy on a gateway computer. After a random number of links work just fine, all
additional links or address entries result in a call to the last working website
(not necessarily google, but google seems to be used a lot. I have added a
screenshot of what happens). The non-host part of the link is added to the
deadlocked host, which results in beautiful 404s.

There are also other reports of this bug using various proxies (AnalogX,
Jana-Server, junkbuster and even provider based proxies) on USENET and several
discussion boards.

The only workaround is to disable proxy and go to direct connection, which is
not always feasible. I'd really like to see this bug confirmed.

I also suggest to alias this bug as "proxy-deadlock" 

Comment 14

[John Schwinghammer]

This is not a bug with Mozilla, as the proxy you are using doesn't support HTTP
1.1, and doesn't give any error messages when HTTP 1.1 is used.

This can be fixed by either updating your proxy (http://www.prixovy.org/) or
going to about:config and changing network.http.proxy.version from 1.1 to 1.0.

*** This bug has been marked as a duplicate of 38488 ***

Comment 15

[Jens Prüfer]

Thanks! Just one small remark ... that should be http://www.privoxy.org/, not
prixovy ;-)

Comment 16

[Matthias Versen [:Matti]]

John : This is not a dupe of bug 38488. bug 38488 is only for the broken
junkbuster while this bug is about a problem qith squid.

Comment 17

[benc]

gustavo, any update here?

Comment 18

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 19

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 20

[benc]

V/ I reviewed the open bugs and there isn't anything else obvious.