Closed
Bug 22890
Opened 25 years ago
Closed 24 years ago
ECONNREFUSED makes chatzilla very sad
Categories
(Other Applications :: ChatZilla, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
Future
People
(Reporter: shaver, Assigned: rginda)
References
Details
If I try to /attach to a server on a bogus port, I get a sprinkling of error
messages about the PR_CONNREFUSED error return, but chatzilla is pretty much toast.
(M12, Win98)
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•25 years ago
|
||
The necko-only socket is part of chatzilla now, so the behavior has changed.
Leaving this bug in because I doubt it does the right thing yet.
Comment 3•24 years ago
|
||
can you be a bit more specific? I don't *think* that you can /attach to a
specific port.
Assignee | ||
Comment 4•24 years ago
|
||
you can use /server <hostname> [[:]port] [pass] to connect to a port, and if you
do that with a bogus port, you should get an error. Even though the code that
shaver referred to is no longer in use, the new code does not handle this
situation correctly either.
Comment 5•24 years ago
|
||
*MASS SPAM*
Changing QA contact on all open or unverified ChatZilla bugs to me, David
Krause, as I am now the QA contact for this component.
QA Contact: rginda → David
Assignee | ||
Comment 6•24 years ago
|
||
superbug checked in, mass marking all dependents fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Other Applications
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•