Use system proxy settings doesn't take care of proxy exceptions list in Gnome proxy settings

[tictactoe]

Binary package hint: firefox-3.0

In Firefox 3 Beta 5 (in Hardy final), when you choose the "Use system proxy settings" in Network options, you grab the proxy address but not the exceptions includes in the System/Proxy setttings !

Is it a Ubuntu Hardy bug ? or a Mozilla Firefox 3 Beta 5 bug ?

[Junior (correojunior)]

I have the same issue.

And this is frustrating.

Any help or solution on this would be appreciated.

Regards,
Jose Luis Jr. Garza

[Alexander Sack (asac)]

On Fri, May 30, 2008 at 03:28:59AM -0000, Junior wrote:
> I have the same issue.
>
> And this is frustrating.
>
> Any help or solution on this would be appreciated.

what do you get when you enter:

env | grep proxy

in a Terminal (e.g. Applications -> Accessories -> Terminal) ?

 status incomplete

 - Alexander

[Junior (correojunior)]

Hi Alexander,

this is what i get when I enter

$ env | grep proxy
http_proxy=http://172.16.200.1:3128/
no_proxy=localhost,127.0.0.0/8,*.local

even if I open a firefo from the same terminal happens the same.

Thanks and regards,
Jose Luis Jr. Garza

[xrayA4T (xraya4t)]

I have the same issue. It is really frustrating as Google desktop uses 127.0.0.1 and I need to switch off the proxy to view it.
Ray

[Alexander Sack (asac)]

On Thu, Jun 05, 2008 at 04:09:36PM -0000, Junior wrote:
> Hi Alexander,
>
> this is what i get when I enter
>
> $ env | grep proxy
> http_proxy=http://172.16.200.1:3128/
> no_proxy=localhost,127.0.0.0/8,*.local

and this is not the same setting that you configured in gnome? not
even after re-logging in?

 status incomplete

 - Alexander

[xrayA4T (xraya4t)]

Hi Alexander,
Ran env | grep proxy and the no_proxy does match what is set in System->Preferences->Network Proxy, it is just that Firefox ignores it.
Ray
b.t.w. My version is:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5

[xrayA4T (xraya4t)]

Hi,
I've just upgraded to RC2 and the problem is fixed.
Ray

[Alexander Sack (asac)]

On Fri, Jun 06, 2008 at 01:21:38PM -0000, xrayA4T wrote:
> Hi,
> I've just upgraded to RC2 and the problem is fixed.
> Ray
>

Is it fixed in rc1 too?

 - Alexander

[xrayA4T (xraya4t)]

Sorry Alexander,
I only discovered yesterday that I could easily upgrade to RC Versions of Ubuntu Firefox so I do not know if it is an issue on RC1. Is there a need to test on RC1? If so I will need a few instructions how to get ahold of a RC1 version of Ubuntu Firefox.
Ray

[Alexander Sack (asac)]

On Sat, Jun 07, 2008 at 04:11:28PM -0000, xrayA4T wrote:
> Sorry Alexander,
> I only discovered yesterday that I could easily upgrade to RC Versions of Ubuntu Firefox so I do not know if it is an issue on RC1. Is there a need to test on RC1? If so I will need a few instructions how to get ahold of a RC1 version of Ubuntu Firefox.
> Ray

Most likely RC1 will be rolled to official hardy-updates archives
today.

 - Alexander

[Junior (correojunior)]

Great!!!

I just have updated my firefox from ubuntu repositories, and now it works correctly.

Thanks Alexander.
---
Jose Luis Jr. Garza

[Alexander Sack (asac)]

On Tue, Jun 10, 2008 at 12:52:06PM -0000, Junior wrote:
> Great!!!
>
> I just have updated my firefox from ubuntu repositories, and now it
> works correctly.
>

thanks for the update

 status fixreleased

 - Alexander

[Mat (madpotato-deactivatedaccount)]

I've installed Firefox RC1 and proxy exceptions still don't work correctly if I "use system proxy settings".

Here's what I do:

1. I set the following exception in Gnome Network Proxy settings (among other exceptions): 72.5.65.0/24

2. I can verify it: by "env | grep no_proxy"
no_proxy=localhost,127.0.0.0/8,*.local,72.5.65.0/24,10.3.0.0/16,10.5.0.0/16,*.mydomain.com

3. I try to open http://72.5.65.144/ and get to my proxy (which does not let me through) instead of the actual web page.

4. When I try the same in epiphany, it works perfectly (I can get to that internal web page).

Could someone please confirm if it's fixed in RC1 or RC2? RC1 definitely has this bug.

[Junior (correojunior)]

Hi Mat,

Correct me if I'm wrong, but 72.5.65.144 is not in range 72.5.65.0/24, right?

If so, just in Gnome Network Proxy settings set 72.5.65.0/144 or something like that

---
Jose Luis Jr. Garza

[tictactoe (xavier-garel)]

Hi Alexander,

Sorry but the problem still exist:
I have done the upgrade to Firefox-3 RC1 from official hardy-updates archives and I still have the same issue.

1- Like Mat, I set some exceptions in Gnome Network Proxy settings

2- I can see the result from CLI with the 'ENV' command : my exceptions are listed in the variable 'no_proxy'

3- Firefox3-RC1 is set with "use system proxy settings" and I can't reach a website concerned by my exceptions

4- I try to logout from gnome then re-enter but no more result !

5- With Epiphany browser there is no problem !

I am waiting the RC2 release to try it out...

Could you update the status of this bug please ?

Thks

---
xgl

[xrayA4T (xraya4t)]

Hi All,
On Ubuntu FF-RC2 if I use manual settings I can add entries like 127.0.0.0/8 and it will bypass proxy. If I switch to use system proxy 127.0.0.0/8 does not work but if I add 127.0.0.1 it does bypass 127.0.0.1.

I could not get any form of wild cards to work on use system proxy. So you will need to add all sites individually rather than using ranges etc.
Ray

[Alexander Sack (asac)]

On Wed, Jun 11, 2008 at 04:12:41PM -0000, xrayA4T wrote:
> Hi All,
> On Ubuntu FF-RC2 if I use manual settings I can add entries like 127.0.0.0/8 and it will bypass proxy. If I switch to use system proxy 127.0.0.0/8 does not work but if I add 127.0.0.1 it does bypass 127.0.0.1.
>
> I could not get any form of wild cards to work on use system proxy. So you will need to add all sites individually rather than using ranges etc.

So the subnet syntax is what is broken here?

 - Alexander

[xrayA4T (xraya4t)]

Hi Alexander,
That appears to be the case. From myself on RC2 and Junior on RC1 it appears that the exceptions are now being read when using System Proxy as they were not in beta 5, but subnet syntax does not, e.g. 127.0.0.0/8. Domain bypass does not work either, e.g. .cnn.com. So full IPs or full host names work as per http://kb.mozillazine.org/No_proxy_for but no form of wild cards or ranges.
Ray

[tictactoe (xavier-garel)]

Hi all,

After few more tests, here is the result for my exceptions :
(env | grep no_proxy) :
no_proxy=localhost,*.local,127.0.0.1,*.lan

With FF3RC1, every hostnames ending with .local or .lan bypass the Proxy : so the wildcard * is accepted by FF3

But it doesn't run if I use 192.168.0.0/16 or 192.168.*

So by now, I can use FF3 with the settings "use system proxy settings".

Maybe the subnet exceptions will run with RC2 or final ?

Thks for your help.

[Alexander Sack (asac)]

On Thu, Jun 12, 2008 at 12:38:44PM -0000, tictactoe wrote:
> Hi all,
>
> After few more tests, here is the result for my exceptions :
> (env | grep no_proxy) :
> no_proxy=localhost,*.local,127.0.0.1,*.lan
>
> With FF3RC1, every hostnames ending with .local or .lan bypass the Proxy
> : so the wildcard * is accepted by FF3
>
> But it doesn't run if I use 192.168.0.0/16 or 192.168.*

How about just using 192.168.0.0 ?

 - Alexander

[xrayA4T (xraya4t)]

Hi,
I tried 127.0.0.0 but it did not bypass 127.0.0.1.
Ray

[Rafał Błaszczyk (rblaszczyk)]

This is not acceptable it's the main system browser - it should seamlessly integrate with environment. Proxy configuration should be clear - it isn't even documented.
I use chromium - it works well with gnome settings and it's still in beta!

[Thomas Schwinge (tschwinge)]

I confirm that I explicitly have to specify 127.0.0.1 in the no_proxy environment variable, instead of the more generic 127.0.0.0/8. Simple hosts (``localhost'') work fine; I didn't check anything else.

[Xavier (xpucel)]

I confirm that using
- Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
- Firefox set on system proxy settings,
- Gnome set up to use a manually configured proxy
- Gnome's ignore hosts lists contains "localhost", "127.0.0.0/8", "*.local" (which are the default Gnome values)
- a local server on port portnb > 30000

Firefox fails to display Urls starting with "http://127.0.0.1:portnb/". It shows an error message from my proxy.
Firefox successfully displays Urls starting with "http://localhost:portnb/".

If I add "127.0.0.1" to the Gnome ignored host list, and refresh the Firefox tabs, it properly displays all the Urls above.

I also believe that by default the proxy should be ignored for local urls (either Firefox should understand 127.0.0.0/8, or Gnome should contain 127.0.0.1).

Thanks for your work.

[jhansonxi (jhansonxi)]

Bug #655025 is probably duplicate. Seamonkey is also affected. Two other browsers using the system settings, Google Chrome and Epiphany, are not.

[Cameron Smith (cameron-smith)]

I don't understand why this Bug is marked as "Fix Released". Where is the fix documented?

I am using FF 3.6.3 on 10.04 ( 3.6.20+build1+nobinonly-0ubuntu0.10.04.1 ) and I get exactly the same behaviour as Xavier reported above in post #24.
 - Individual ignore host entries are handled correctly
 - wildcard or CIDR subnet entries are NOT handled correctly