Nicolas Mailhot wrote:
You do need to auto detect proxy settings - when a proxy is
available
most of the times you won't be allowed direct internet connection.
The problem is firefox sucks big time when you're behind a proxy - as
soon as the proxy is slow to answer for one tab all the others start
being sluggish/frozen (I suppose firefox has internal locking where
the cost of some locks is only evident in a proxy context)
The problem is not the setting, the problem is firefox is buggy.
That's something to report upstream.
I experienced this problem to. My guess was that Firefox blocked while
resolving hostnames in proxy.pac JavaScript snippets like this one:
function FindProxyForURL(url, host)
{
ip = dnsResolve(host);
if (isInNet(myIpAddress(), "10.0.0.0", "255.0.0.0")
&& !shExpMatch(url, "ftp://*")
&& !isInNet(ip, "127.0.0.0", "255.0.0.0")
&& !isInNet(ip, "10.0.0.0", "255.0.0.0")
&& !isInNet(ip, "81.174.33.43", "255.255.255.248"))
return "PROXY 10.3.3.1:3128";
else
return "DIRECT";
}
--
\___/
|___| Bernardo Innocenti -
http://www.codewiz.org/
\___\ One Laptop Per Child -
http://www.laptop.org/