Closed Bug 22890 Opened 20 years ago Closed 19 years ago

ECONNREFUSED makes chatzilla very sad

Categories

(Other Applications :: ChatZilla, defect, P3)

x86
Windows 98
defect

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)
Status: NEW → ASSIGNED
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.
mass marking chatzilla bugs future
Target Milestone: --- → Future
can you be a bit more specific? I don't *think* that you can /attach to a
specific port.
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.
*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
Depends on: 71468
superbug checked in, mass marking all dependents fixed.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.