36265 - Proxy: no error if manual http proxy is wrong

Status: VERIFIED WORKSFORME

(Core :: Networking, defect, P3)

Description

[vectro]

From Bugzilla Helper:

User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.10 i686; en-US; m15)

BuildID:    2000041811



When I (accidentally) put in the wrong port for my HTTP proxy in proxy

configuration, I got an error on the console, but no dialog was presented trying

to load pages.







Reproducible: Always

Steps to Reproduce:

1. Set incorrect HTTP proxy settings (e.g. wrong port)

2. Try to load a page

3. Note how no error is displayed, but page fails to load.



Actual Results:  As described above.	



Expected Results:  Same thing as netscape 4; It should present an error. It

wouldn't even be a bad idea to try to contact the proxy before accepting the

proxy settings.

Comment 1

[Chris Siebenmann]

 Still happens on a recent Linux CVS build.

 I suspect that the root cause is the same thing as bug #37991,
and possibly one should be considered a dup of the other, since
both seem to be basically 'no error alert is generated when the
network layer cannot contact the target' (whether the target is
an actual web server or a proxy).

 This also occurs if the target IP is bad (nonexistent), instead
of the target IP being up and refusing connections on the chosen
port.

Comment 2

[Gagan]

nsbeta3-

Comment 3

[Jesse Ruderman]

See also bug 56629.

Comment 4

[Darin Fisher]

[linux netscape 6.0 build]

While no proxy specific failure message is reported, the connection attempt
will fail with a dialog saying unable to connect to specified host (or
something similar).

Comment 5

[Peter Janes]

cc myself.  Also, this is still in Mozilla trunk build, Linux 2000120508.

Comment 6

[benc]

Connection failures should clearly point to the root cause (or failed step in
the process).

keying nsbeta1

Comment 7

[[e-mail]]

Proxy does generate an error now, but it is the wrong error (it says connection
to the destination failed even if the proxy connection is the root cause).

This is bug 55629.

Failures of the secondary connection and how the errors are returned to the
client are in bug 2875.

Comment 8

[[e-mail]]

I get errors when my proxy is unavailable now. Gettin the correct error is the
topic of a different bug.

Comment 9

[benc]

qa to me.

VERIFIED:
Mozilla 0.9 Win+Linux+Mac
an error message is provided if you specify the wrong port:

"The connection was refused when attempting to contact <hostname>".

No mention of the proxy connection being the point of failure, but it is an error...