Closed
Bug 180472
Opened 22 years ago
Closed 22 years ago
uninformative "connection refused" message
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 152781
People
(Reporter: marekj1, Assigned: darin.moz)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021115 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021115 wheather server is down or connection timeout or for some other errors I always get "connection refused" message. The message should be different - for begginer user I might suggest that server doesn't like this user. Most of the time I get this message it's because connection timed-out Reproducible: Always Steps to Reproduce: 1. 2. 3.
(I should have read it before posting) there should be more messages according to situation and should be more accurate. connection refused should only happen when connection was ok but there was http error like 403 (or 401) if there was timeout - message should be connection timeout not connection refused as it is currently
Hi, All web browers do that it is not a message that your web browser creates it is a message that the web site cerates so maybe we can try to make a program that will do that but I do not think so. And a connection time out is where you are denied to the server and not the connection being lost to the server.
Comment 3•22 years ago
|
||
if we ignore bryans comment.. Are you sure that you got a 401/403 ? -> Http
Assignee: asa → darin
Component: Browser-General → Networking: HTTP
QA Contact: asa → httpqa
90% of times I get the message because of connection timeout. "Connection refused" suggests "don't refresh, because it won't work" but it works for me almost always, except for 10% when the server is actually down. After revising I think it's more like 99% than 90%
to: Matti (if you want marquee use IE) All I was saying was "Connection refused" seems most accurate for 403 (althought 403 - doesn't mean connection is refused only access to that page) Problem is I get "connection refused" when it actually should say "connection timeout"
Comment 6•22 years ago
|
||
this is a problem - mozilla says "connection refused" for a whole bunch of network errors, most of which aren't connection refused. *** This bug has been marked as a duplicate of 152781 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Are you talking about connection establishment timeout, or an existing connection doing a timeout? The reason I ask is that the connection establishment timeout error is pretty accurate text.
"Connection refused" may be one of the reasons for "connection timeout" But in my case for 99% of times it's timeout waiting for response from server (like due to large traffic and poor server's throughput). I'm not sure what do you mean by "existing connection doing a timeout", but if you mean for example timeout when sending a large blob in one chunk - it happens very rarely, and that's not what I mean.
You need to log in
before you can comment on or make changes to this bug.
Description
•