858854 - Manual settings for socks host/port supersede system proxy setting

Status: RESOLVED DUPLICATE of bug 849792

(Core :: Networking, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 02/17 - 02/21)]

Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20130405 Firefox/22.0 ID:20130405004016 CSet: 272dd16b0d95

I have upgraded my Aurora version to the new 22.0a2 today and since the restart Firefox is not able to connect to the network anymore. It claims that a proxy server is refusing the connection. The only setting I have in Firefox is the system proxy, and in the Gnome settings no proxy is selected.

When I use the same Aurora version with another profile which also has the system proxy set, everything works fine. So I have started Aurora in safe mode with my default profile but that doesn't make a difference.

I will dive through the preferences the next days which might give us a clue what could be the reason for that behavior.

The failure I get:

The proxy server is refusing connections
Firefox is configured to use a proxy server that is refusing connections.

Check the proxy settings to make sure that they are correct.
Contact your network administrator to make sure the proxy server is working.

Comment 1

[Patrick McManus [:mcmanus]]

can you send me the prefs.js from your profile? (or just grep it for proxy)

I wonder if you have some inconsistent config fragment that is causing a problem (e.g. a socks port number defined even after you have said don't use socks) or something along those lines

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 02/17 - 02/21)]

Good call regarding socks host/port. That was indeed the problem. But those were entered sometime ago when I had the setting enabled for manual proxy settings. I switched back to system proxy a while back, so any manual setting shouldn't have an effect for Firefox. But as it seems a check for the socks host doesn't care about that and still uses the inactive setting.

So that's indeed a regression in 22.0a2.

Steps:
1. Create a fresh profile
2. Edit proxy settings and define a socks host/port in manual settings
3. Switch to system proxy settings
4. Try to load a page

Starting with 22.0a2 we fail to load the page now.

Comment 3

[Patrick McManus [:mcmanus]]

you don't have to bother with the regression window.. Its probably a side effect of making socks changes dynamically visible and I suspect just exposed this latent bug.. I actually think its a dup of something on file. I'll try and get to it this week

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 02/17 - 02/21)]

Don't worry it's a quick check. Here the results:

PASS: 130309 http://hg.mozilla.org/mozilla-central/rev/e6215e0357fa
FAIL: 130310 http://hg.mozilla.org/mozilla-central/rev/9e6232e86000

Changelog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e6215e0357fa&tochange=9e6232e86000

There is only one proxy related change in there which is bug 824341.

Comment 6

[Alex Keybl [:akeybl]]

(In reply to Karl Tomlinson (:karlt) from comment #5)
> 
> *** This bug has been marked as a duplicate of bug 849792 ***

Are you sure about this? FF18 is affected by bug 817533, but FF21 is marked as unaffected here.

Comment 7

[Karl Tomlinson (:karlt)]

I'm sure this is a duplicate of bug 849792.

Bug 849792 describes the same symptoms of the same bug as 817533, which now demonstrates in a new situation.

Comment 8

[Alex Keybl [:akeybl]]

OK - let's continue the conversation in bug 849792.