887546 - Firefox 22.0 using Manual proxy configuration even though it's set to use system settings

Status: RESOLVED DUPLICATE of bug 817533

(Firefox :: Untriaged, defect)

Description

[José Carvalho]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130620122336

Steps to reproduce:

Under Preferences > Advanced > Network > (Connections) Settings, choose the option "Manual proxy configuration" and fill in any host and port.

The host doesn't need to actually exist -- in fact it's easier to test if it doesn't -- but the host name must not be empty and the port most not be left as zero, otherwise Firefox will behave as expected.

Make sure you select "Use system proxy settings" before closing the dialog.


Actual results:

When you navigate to any page, Firefox will use the proxy under manual configuration, although it should be using the OS' proxy settings. If you've configured Firefox to use an unexistent machine, you'll get an error page reading:
« Unable to find the proxy server
Firefox is configured to use a proxy server that can't be found. »

In the particular case of the person who's called my attention to this issue, an authentication prompt came up from a proxy she hasn't used since many years ago.

Note: The bug manifests regardless of whether you choose to specify an HTTP proxy, FTP proxy or SSL proxy, as long as you then try to access a URL with the corresponding protocol.
I should point out my system settings amount to using no proxy at all. So do the settings of the person I refer to above. I haven't tested with different settings.


Expected results:

The browser shouldn't be using the proxy settings under manual configuration when the radio button is not set to that option. It should be using the OS' settings.

Comment 1

[José Carvalho]

Meanwhile I've read bug 817533 and it looks like this one may be a duplicate. 
I apologize for not having seen it before, I was unaware that Bugzilla by default skips searching among bugs marked "resolved".

I'm marking this bug as a duplicate, but I hope bug 817533 changes status from "verified fixed", as it very much *isn't* fixed.

Comment 2

[Karl Tomlinson (:karlt back Feb 10)]

No need to apologize :) It's easy to mark duplicates.