Closed Bug 166487 Opened 24 years ago Closed 23 years ago

Intermittent incorrect "connection refused" errors

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: sharding, Assigned: darin.moz)

Details

As I said in the comments, this may be related to Bug 165339. However, it sounds like the reporter is seeing the problem 100% of the time, while it's relatively rare for me. So I'm going on the assumption that we're seeing something different. Every so often, Mozilla will report that the connection was refused by the server for a page I'm attempting to load. Trying a second time to load the page always works. This happens about four or five times a day; I'd estimate it happens every 50-100 loads. It also seems to happen with some image loads (a known good image on a page won't load the first time). This did not start until I installed a new build on August 29. I am working behind a firewall. However, I am relatively confident that the firewall is not causing the problem for three reasons: 1. The firewall software and hardware have not changed since this was last working correctly. 2. The firewall does not log any blocked packets corresponding to the errors. 3. These errors don't appear in any other web browser or other application operating behind the firewall. Unfortunately, I have not managed to catch one of these errors with tcpdump to see if any packets are being sent at all. I tried unsuccessfully for a couple of hours tonight. I'll keep trying. I'm currently using build 2002082909 on MacOS X 10.2.
Sean, have you tried toggling the keep-alive and pipelining options in Advanced/HTTP Networking?
No, I have not. I'll give that a try and see what happens.
Turning off keepalive definitely doesn't fix the problem. Now I've turned keepalive back on and turned on pipelining (which wasn't on before) to see if it helps.
Just happened to me with pipelining on too. So, no, those settings have no effect on this bug.
Sean, can you still reproduce this problem using a current nightly build?
No, I don't remember having seen this problem for a long time. We should close this bug.
Resolving WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.