Closed Bug 49718 Opened 26 years ago Closed 26 years ago

Socks proxy causes weird "connection refused" messages

Categories

(Core :: Networking, defect, P3)

x86
All
defect

Tracking

()

VERIFIED DUPLICATE of bug 48357

People

(Reporter: semperubisububi, Assigned: gagan)

References

()

Details

I was trying to use Mozilla M17 from work on my linux box, it works fine with our http proxy (though our http proxy is dog slow and only works for parts of the day), but with socks it says connection refused constantly. Especially when submitting forms (but not exclusively, this may be a red herring). Unfortunately our socks is the only fast one. I had this same problem on Win 2k with Netscape 6.0 PR2. The same socks proxy works fine with the most recent Communicator for both Linux and Win 2k. I cant wait for mozilla to get this fixed and java support for both linux and windows up to spec, then life will be really good.... In the log it would just say error connecting. Sometimes that would happen even though it loaded the page.
dup of 48357: "frequent 'connection refused' messages when connecting through a socks proxy" *** This bug has been marked as a duplicate of 48357 ***
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Verified dupe of bug 48357
Status: RESOLVED → VERIFIED
Did using a SOCKS connection fail for ALL network access or some network access? We need more information to analyze problems like this. If this problem does not currently affect you, please update this bug. You might want to consider using a standard set of steps like a test case to report problems: http://www.packetgram.com/pktg/proxy/genericproxytest.html
This no longer affects me as I'm no longer behind a socks proxy. However, to answer your question it was frequent and unpredictable. I gave the urls for some sites it happened on and described in my original description that it happened sometimes after the page displayed correctly. Sorry I can't be much help, I use ipchains for my home network and business network.
You need to log in before you can comment on or make changes to this bug.