129501 - SOCKS: No "connection refused" error for unresponsive ports

Status: NEW

(Core :: Networking: Proxy, defect, P5)

Description

[benc]

Mozilla 098 (running necko functional tests)

STEPS:
Configure manual proxy for working SOCKS 5 server.
Connect to URL w/ wrong port (e.g. port 81) that is non responsive.

OBSERVED BEHAVIOR:
You do not receive an error message. The trobber runs briefly then stops.

EXPECTED BEHAVIOR:
With a direct connection, you receive a "Connection refused" error.

Comment 1

[benc]

confirmed Win98 and Linux

Comment 2

[benc]

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.

Comment 3

[Dale Williams]

Build 2002041711.  Mac OS9.1
The "Connection Refused" dialog box comes up, but in an annoying way.  (For
example, I've opted OUT of the 'Doublclick' ads.  When I visit
'rollingstone.com', the "conection refused from ad.doublclick.com" appears twice
while the page loads.  Both dialogs require a positive response before Mozilla
proceeds.
Better would be Apple's built in error message facillity (the yellow boxes used
for non-critical errors), or something likeInternet Explorer--  Logging the
non-critical but interesting errors to a log file..

In the case of ad.doubleclick.com  I'd much rather just have  the page loadd
wtith a blank placeholding box filled with an X.  (This is IE's default for this
error.)

Comment 4

[benc]

Dale:

Are you using socks?

Comment 5

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258