Closed Bug 219945 Opened 22 years ago Closed 22 years ago

Conn: waits forever instead of "connection failed" message when nothing listens to destination port

Categories

(Core :: Networking, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 219150

People

(Reporter: spiros_ioannou, Assigned: darin.moz)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030917 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030917 In the latest nightlys (including today's) when connecting somewhere where there's no web server listening, instead of the "connection refused" message the browser hangs in the "connecting to xxx.xxx.xxx.xxx" state forever The same happens with every port, not just the 80. Very irritating when you have redirected all ad-related sites to 127.0.0.1 because nothing works :-) Reproducible: Always Steps to Reproduce: 1.If not running a web server to your host try http://127.0.0.1 2. 3. Actual Results: the browser hangs in the "connecting to 127.0.0.1" state forever. Expected Results: immediately show "connection refused".
*** This bug has been marked as a duplicate of 219150 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Summary: browser waits forever instead of "connection failed" message when nothing listens to destination port → Conn: waits forever instead of "connection failed" message when nothing listens to destination port
You need to log in before you can comment on or make changes to this bug.