Hi,
We are experiencing some proxy access issues when using EO.Web at a number of client sites.
The proxy is implemented using a PAC file that looks like this:
Code: JavaScript
var proxy = "PROXY PROXY1:9000; PROXY PROXY2:9093; // more IPs:Ports....";
// Default localhost for denied connections
var deny = "PROXY 127.0.0.1:65535";
// Bypass the proxy server and try to connect directly via local network
var bypass = "DIRECT";
function FindProxyForURL(url, host)
{
//
//By default, all aa.com child domains are trusted. Only list third-party domains which are not part of aa.com.
//
alert('checking host='+host);
if (
shExpMatch(host, "*.aa.com*")
|| shExpMatch(host, "*entrust.net*") // added for access thru Firefox
// more authorized domains...
)
// If the host is defined return the proxy list, else bypass the proxy and try to connect via local network.
return proxy;
else
{
alert('bypass host='+host);
return bypass;
}
}
When we used IE we could access our sites, but any other browser failed.
We were able to troubleshoot the issue with Firefox because all the alert(...) calls were reported in the web console of the browser. And we found out that we needed to add *entrust.net* in the white list. That was enough for Firefox to access all our sites.
However we were not able to resolve the problem with EO.Web engine. I tried to add in the native options log settings:
--log-level=0 --log-net-log=c:\temp\MyNetLog.txt but that did not produce any log and the web console did not report any log eiter - unlike with Firefox.
I am not sure at this point if it is a EO.Web issue or a Chrome one. Unfortunately the client machines I had access did not allow to install Chrome native for me to make that distinction.
I suspect this is a Chrome issue anyway because I read some forums mentioning its proxy implementation may differ from IE.
In any cases, I would be very grateful if you had any advice on how to troubleshoot this proxy access. I just need to log what sites are being inspected by our pac script and which ones are rejected and falling in the bypass category.
I also tried to invoke
window.console(...) in place of alert but that was breaking the pac scripting.
For now we serve our sites using Firefox, needless to say this has to be a temporary work around as we need to run our EO.Web wrapper at those client sites.
As always, thank you very much for your input on this matter.