GNOME Bugzilla – Bug 78940
Automatic proxy settings not used when loading the first url
Last modified: 2004-12-22 21:47:04 UTC
when galeon is trying to recover from a crash, it reopens all the windows with the old url's but it doesn't use the proxy settings to go to them. when I then type the url in the location field manually and press enter an authentication box for the proxy pops up, and everything works as it should. my crash recovery settings: Recover from crashes: ask user How to recover: Reopen windows Network settings: automatic proxy config (uses authentication)
Could you please upgrade to the latest mozilla and galeon releasess and test this again
A debian user kindly tested this form me per my request after filing a report against 1.0.3 and this is what he had to say: If I call galeon from, say, a shell: galeon www.slashdot.org ...it works fine. It goes to my auto-proxy, grabs the cache information, and then uses it to go out. However, and this is amusing, if I use a Gnome link (say, click on something from Evolution, or maybe slashapp), it doesn't. The behaviour is similar; it makes a connection to the auto-proxy server, grabs the cache information, and then (apparently) disregards it and tries to go directly. So, it's not consistent behaviour (but is consistent depending on how it's called, if that makes sense), and may in some way be linked with how Gnome (?) is calling the application. My gnomecc tells me it's just, 'galeon "%s"' which seems about right, so it's really bizzare. I don't set any environment variables for cache, which was a thought that crossed my mind. But investigating environment variables that effect Galeon might be useful (as the way it's called is similar from my shell test and my Gnome-link test).
And then someone else tested more and said: Using galeon 1.2.0, I always get the proxy error whatever I do. For any site, whether run from gnome-terminal or ROX's panel, and whether I specify the URI as an argument or just let it reopen the existing setup. I normally have http_proxy set, but unsetting it gives the same effect. In any case, going to a site once galeon is running works fine. Also, running galeon when a copy is already running works fine. This is all with the proxy set to 'Auto'. If it's set to 'Manual' then it works fine!
masschange ganeral -> galeon-maint@bugzilla.gnome.org (which is currently me) sorry for the spam
*** Bug 82392 has been marked as a duplicate of this bug. ***
from the duplicate above: When I start up galeon, I have about a dozen tabs that the program loads pages for. Three of these always fail to load. These three are loaded from my company's internal web site through a ssh proxy, while all the others are loaded directly. I know the proxy is working because I'm running VNC over it at the same time. If I stop the file loading, click in the URL window, and hit return, the page loads immediately. Its as if the page loading attempts are initated before the proxy settings are read. Here's the contents of my automatic proxy file: function FindProxyForURL(url, host) { if (dnsDomainIs(host, ".cisco.com") || localHostOrDomainIs(host, "127.0.0.1")) return "PROXY localhost"; else return "DIRECT"; }
We really need to know if mozilla behaves the same.
*** Bug 82841 has been marked as a duplicate of this bug. ***
*** Bug 83526 has been marked as a duplicate of this bug. ***
It seems like galeon doesn't set the proxy _early_ enough. At least one of these http://bugs.debian.org/149673 http://bugs.debian.org/134839 http://bugs.debian.org/139428 reports stated, that when restoring a session (for example after a crash) or calling galeon from the command line (when not running) causes the page load to fail (due to missing proxy) - reloading the page then succeeds (so proxy is set then?) This probably should be fixed for 1.2.6?
I have applied a fix to cvs which should solve this problem. I need confirmation that it is indeed fixed.
reported to be not fixed by two debian users affected.
The current bug is 99923 *** This bug has been marked as a duplicate of 99923 ***