socket transport misinterpreting connection errors

RESOLVED WONTFIX

Status

()

Core
Networking
P3
normal
RESOLVED WONTFIX
16 years ago
2 years ago

People

(Reporter: kaie, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Implement "no route to host" error message as described in bug 106188.

Comment 1

16 years ago
More precisely, the current nsSocketTransport.cpp code
always reports "Connection refused by peer" when a
connection setup failed.  But "Connection refused by
peer" is just one of the possible reasons.  There are
also "Connection timed out", "No route to host", etc.

Updated

16 years ago
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Implement "no route to host" error message → socket transport misinterpreting connection errors
Target Milestone: --- → mozilla1.0

Comment 2

16 years ago
The "connection refused" is reported even if the connection is closed before any
data is sent by the server. That is, of course, long after the connection setup.

try "netcat -l -p 1234"  and in mozila http://127.0.0.1:1234/askdfjhdkfjh and
then killing netcat with Ctrl+C or kill -TERM.

Comment 3

16 years ago
pushing this out post 1.0... will pull it in if time permits.

-> 1.0.1
Target Milestone: mozilla1.0 → mozilla1.0.1

Updated

16 years ago
Target Milestone: mozilla1.0.1 → ---

Comment 4

16 years ago
mass futuring of untargeted bugs
Target Milestone: --- → Future

Comment 5

12 years ago
related: bug 217792

Updated

12 years ago
Assignee: darin → nobody
Status: ASSIGNED → NEW
QA Contact: benc → networking
Target Milestone: Future → ---
this granularity won't help our users
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.