Closed
Bug 164283
Opened 22 years ago
Closed 19 years ago
gopher: no connection establishment timeout error
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: sluggo, Assigned: dougt)
References
()
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
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.
QA Contact: benc → gopherqa
Summary: Gopher URLs timing out → gopher: URLs timing out
Comment 1•22 years ago
|
||
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 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
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?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 4•22 years ago
|
||
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•22 years ago
|
||
Comment 6•22 years ago
|
||
Isn't this a dupe of Bug 149322?
"gopher: Page doesn't load in Mozilla, but does in IE"
-> 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.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.4a?
Keywords: clean-report
Summary: gopher: URLs timing out → gopher: no connection establishment timeout error
Updated•22 years ago
|
Flags: blocking1.4a? → blocking1.4a-
Comment 8•19 years ago
|
||
Works on current trunk.
Status: NEW → RESOLVED
Closed: 22 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•