When a proxy server is configured and cannot be reached, the wrong error message "The document contains no data" is shown in an alert box. This will probably confuse a lot of users and is simply wrong. This seems to be relatively new: it happens with the 1.3b on linux and NT and the 20030212/linux trunk build. It does not happen with the 20021211/linux build which gives the correct error message ("The connection was refused when attempting to contact the proxy server you have configured. Please check your proxy settings and try again").

dup of bug 189965? See bug 192825 comment 4

Yes, seems to be related to 189965 but this bug has a description and comments that make it hard to find, given these symptoms. Since this is also a recent regression we should make sure that the original error message reappears when this bug gets fixed. So how about leaving this open to make it easier for others to avoid further DUPes and DUPing this bug when and if the error gets fixed through the patch in 189965?

it's 99% a dupe. YOu can reopen if bug 189965 is fixed and you still get this .. *** This bug has been marked as a duplicate of 189965 ***

Still seeing this in 20030214/linux though bug 189965 was fixed on trunk on Feb 13th.

reopening because this seems to be not fixed

-> me

WORKSFORME win2k 2003021608. i tried configuring a HTTP proxy to 127.0.0.1:8080 with no proxy server listening on that port. that gave me the "connection refused to proxy server" error dialog as expected. interestingly enough, i was able to repro the problem using a debug CVS build under linux. investigating...

ok, this bug will be fixed when the patch for bug 193267 lands.

fixed now that my patch for bug 193267 has been checked in.

The behavior is still strange when the proxy is configured as an IP that cannot be reached (1.2.3.4:2000). In this case, the error message is: "the connection timed out when trying to reach <URI of the target link, not IP of the proxy>". If the proxy is set to an (currently) non-existing IP like 192.168.1.50:2000, no error message whatsoever is displayed, Mozilla shows the busy indicator for a short time, then the original page is shown as if nothing had happened. This situation will occur when the proxy runs on the local LAN and the machine is off the LAN.

yeah, we only implicate the proxy server when there is a connection refused or a DNS lookup failure. we should probably do the same for proxy connection timeouts.

Bug 197697 for the timeout error.