164283 - gopher: no connection establishment timeout error

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Kim Scarborough]

Any gopher URL I go to just shows the URL in the page; the menu never comes up.
It just sticks on "Sending request".

Using build 2002082308, but I saw this in the 8/13 build too.

Comment 1

[Michael Lefevre]

not sure if this is actually the same bug, but it's definitely broken in recent
builds...

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

Comment 2

[benc]

WFM, Win 98, Mozilla 1.2.1.

The other gopher bugs seems to not WFM as much.

When it gets stuck like this, does it ever time out for you?

Comment 3

[benc]

-> default owner.

Comment 4

[Michael Lefevre]

no, never times out (at least not after 5 minutes or so). also doesn't stop when
stop button is clicked.

if I open mozilla and go straight to a gopher URL, it works. opening other pages
first, and then going to a gopher URL, it never completes - Index of <url> is
displayed, then 2 horizontal rules, and then it stays like that, with "sending
request in the status bar".

tried turning logging on, but i can't see that it says much of use. i'll attach
the log anyway...

Comment 5

[Michael Lefevre]

Attachment: log file (logging all)

Comment 6

[Prognathous]

Isn't this a dupe of Bug 149322?
"gopher: Page doesn't load in Mozilla, but does in IE"

Comment 7

[benc]

-> NEW, +clean-report, requesting for 1.4a.

I've changed the URL so it points to a currently unused IP address. You don't
need to navigate to find a test URL now.

A quick look suggests this is separate from the other bugs mentioned, so not
duping was the right idea.

This problem has gotten worse in 1.3x, before nothing happened except a status
update. Now, the index/html is displayed w/ no entries when the timeout occurrs,
suggesting an empty gopher server!

This bug is also probably blocked by other gopher content-level bugs, but I
haven't looked at that yet.

Comment 8

[Eli Friedman]

Works on current trunk.