87811 - Status bar erroneously says "Resolving host"

Status: VERIFIED DUPLICATE of bug 85551

(Core :: Networking, defect)

Description

[Brad Garcia]

When mozilla is attempting to contact a web server,
the status bar continues to say "Resolving host ...".
However, I'm sure that the host name has already been resolved,
and at this point it is simply trying to contact the server.

The status bar should be updated to say "Contacting host ...".

Currently, the slashdot.org webserver is down, so it makes a good
test case.  I can resolve it easily, and even ping it successfully,
but it doesn't respond to http requests at all, causing mozilla to
time out after several seconds.  The "Resolving" message is visible
until we hit the timeout.

Comment 1

[R.K.Aa.]

Are status-bar messages are out of synch? When a host *has* been resolved, i
sometimes see "transfering data from.." for minutes on end, without there being
any network traffic at all. Then suddenly a brief "connecting to" as the data
suddenly starts to pour in. (current linux CVS)

Comment 2

[James Paige]

I think this bug is a symptom of bug 85551

Appearently, the networking component IS updating the status when the address
gets resolved, but the status bar is failing to repaint it until later, for
whatever reason.

Comment 3

[Boris Zbarsky [:bzbarsky]]

This is either bug 85551 or bug 72805 depending on the build Brad is using
(Brad, you should really include your build ID with the bug report). 

Resolving duplicate.

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

Comment 4

[rbs]

Verified dup - that's exactly what bug 85551 is about. Status bar messages 
sometimes seem out of sync.

Comment 5

[Brad Garcia]

Sorry about leaving out the build info:

linux x86 2001-06-07-21

I also apologize for submitting a dup.  I tried searching on "Resolving"
and didn't find anything appropriate.

Comment 6

[Boris Zbarsky [:bzbarsky]]

Brad, it's OK.   Dups happen to everyone.  The reason the bug with "Resolving"
in its summary did not come up (bug 72805, which this is actually a duplicate
of, based on the build id) is that it was fixed and the default query searches
only bugs that are still open....

Thanks for using Mozilla and reporting bugs!  It's the only way to make the
browser better.  :)