Closed
Bug 29367
Opened 26 years ago
Closed 26 years ago
OnStopRequest() not getting called with NS_ERROR_CONNECTION_REFUSED
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
M16
People
(Reporter: sspitzer, Assigned: jud)
Details
(Whiteboard: 2d)
Attachments
(1 file)
|
962 bytes,
patch
|
Details | Diff | Splinter Review |
when I fixed #26773, added support for alerts when the protocols OnStopRequest()
got called with aStatus == NS_ERROR_CONNECTION_REFUSED or NS_ERROR_NET_TIMEOUT
but, when I went to test it, I never saw OnStopRequest() getting called with
those values.
the result: if the user's mail/news server request to connect times out or is
refused, the user will not get an alert.
Comment 1•26 years ago
|
||
On sending mail, this can result in loss of data (user not warned that sending
message failed when server refused connection). Upping to major.
Note: I did see a connection time out warning on sending mail on Linux build
2000.02.26.08.
Severity: normal → major
Comment 2•26 years ago
|
||
Is this a general necko problem, or particular to a mail/news protocol?
| Assignee | ||
Comment 3•26 years ago
|
||
I just verified that this still works in HTTP (try to access
http://obob.netscape.com). I'm not sure what the problem could be. Are you sure
you're hitting a server that is refusing connection or timing out?
Comment 4•26 years ago
|
||
I see a time out both on http and in mail. When the server refuses the
connection, I don't get an error. Try http://h2so4.dhs.org/ . Console says
Document http://h2so4.dhs.org/ loaded successfully
although I sure as hell have port 80 closed.
| Reporter | ||
Comment 5•26 years ago
|
||
changing summary, connection timed out is working.
Summary: OnStopRequest() not getting called with NS_ERROR_CONNECTION_REFUSED or NS_ERROR_NET_TIMEOUT → OnStopRequest() not getting called with NS_ERROR_CONNECTION_REFUSED
| Reporter | ||
Comment 6•26 years ago
|
||
here's proof of the connection refused problem
$ telnet sspitzer 11
Trying 208.12.40.110...
telnet: Unable to connect to remote host: Connection refused
from 4.x, http://sspitzer:11
you get an alert about access to the port given has been disabled for security
reasons.
from 5.0, nothing loads, and on the console you get
Document http://sspitzer:11/ loaded successfully
this be re-assigned to one of you necko gurus.
Updated•26 years ago
|
Target Milestone: M15
Comment 9•26 years ago
|
||
Mass moving to M16 to get these off the M15 radar. Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
| Assignee | ||
Updated•26 years ago
|
| Assignee | ||
Comment 10•26 years ago
|
||
hmm. This used to work. I've added (attachment) an extra case to catch the _HUP
signal and this is working for me on windows and linux. I haven't tested
mail/news though, can someone please test the patch in that scenario.
Keywords: beta2
| Assignee | ||
Comment 11•26 years ago
|
||
| Assignee | ||
Comment 12•26 years ago
|
||
fix is in.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 13•26 years ago
|
||
fix is out. I think this was causing some unpleasantness in today's builds.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 14•26 years ago
|
||
fixed.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•