Open Bug 129502 Opened 23 years ago Updated 2 years ago

SOCKS: "Connection refused" error when "Timeout" should be returned

Categories

(Core :: Networking, defect, P5)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
UNCONFIRMED
Milestone:
Future

People

(Reporter: benc, Unassigned)

References

Details

(Keywords: helpwanted, Whiteboard: [necko-would-take])

STEPS: Configure manual proxy for valid SOCKS 5 server. Connect to unused IP address. OBSERVED: "Connection refused" error returned. EXPECTED: "The operation timed out when attempting to contact <IP address>."
confirmed allplats
Keywords: helpwanted
OS: Windows 98 → All
Hardware: PC → All
Temporarily "futuring" all PAC&SOCKS bugs to clear new-networking queue. I will review later. (I promise) If you object, and can make a case for a mozilla 1.0 fix, please reset milestone to "--" or email me.
Target Milestone: --- → Future
Probably the same as bug 40497, resolving as dupe since notthing seems tobe happening here. *** This bug has been marked as a duplicate of 40497 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
REOPEN: This is for a SOCKS config.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Wow, No wonder I didn't see this bug when reporting mine, it's over 5 years old. As I noted in #402838 people are bitching about near-instant connection timeouts because the error message is wrong. This would resolve a number of percieved proxy errors by providing the appropriate messages - and that can't be too difficult, can it?
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Severity: normal → S3

Moving back to unconfirmed since it's unclear if this still is the case

Status: REOPENED → UNCONFIRMED
Ever confirmed: false
You need to log in before you can comment on or make changes to this bug.