I confirm (that for me) the problem is proxy.pac related.
Up to now, I denied the access to www.mysite.com/proxy.pac for when users are outside, with their netbooks.
My Apache .htaccess looked like:
<Files proxy.pac> Order Deny,Allow Deny from All Allow from 192.168.0.0/16 </Files>
This worked for Chromium+IcedTea but not for Firefox+IcedTea.
Finally I had to use a new .htaccess like:
Options +FollowSymLinks RewriteEngine On RewriteCond %{REMOTE_ADDR} !^192\.168\. RewriteRule proxy\.pac$ http://www.mysite.com/direct.pac [R=301,L]
where direct.pac is:
function FindProxyForURL(url, host) { return "DIRECT"; }
Finally, Chromium+IcedTea don't understand the possibility to return more than a proxy (or proxy fail).
I had a proxy.pac ending by:
return "PROXY 192.168.0.3:8080; DIRECT";
and I had to put:
return "PROXY 192.168.0.3:8080";
I confirm (that for me) the problem is proxy.pac related.
Up to now, I denied the access to www.mysite. com/proxy. pac for when users are outside, with their netbooks.
My Apache .htaccess looked like:
<Files proxy.pac>
Order Deny,Allow
Deny from All
Allow from 192.168.0.0/16
</Files>
This worked for Chromium+IcedTea but not for Firefox+IcedTea.
Finally I had to use a new .htaccess like:
Options +FollowSymLinks www.mysite. com/direct. pac [R=301,L]
RewriteEngine On
RewriteCond %{REMOTE_ADDR} !^192\.168\.
RewriteRule proxy\.pac$ http://
where direct.pac is:
function FindProxyForURL (url, host) {
return "DIRECT";
}
Finally, Chromium+IcedTea don't understand the possibility to return more than a proxy (or proxy fail).
I had a proxy.pac ending by:
return "PROXY 192.168.0.3:8080; DIRECT";
and I had to put:
return "PROXY 192.168.0.3:8080";