Windows 10 with GPO and mandatory PAC Proxy : Chrome unable to find Proxy unless --winhttp-proxy-resolver is given.
Reported by
vincent....@gmail.com,
Jan 15
|
|||
Issue description
Chrome Version : 71.0.3578.98 (Official Build) on Windows 10 1803
URLs (if applicable) : Every single URL is a FAIL unless I force Chrome to use winhttp (--winhttp-proxy-resolver)
Other browsers tested:
Safari: N/A
Firefox: OK (system proxy settings)
Edge: OK (system proxy settings)
Seamonkey: OK (system proxy settings)
Chrome: FAIL (Had to manually edit desktop shortcut to add --winhttp-proxy-resolver)
What steps will reproduce the problem?
(1) Use GPO to Configure Proxy settings: Auto-configuration URL only to PAC file: http://hostname.domain.name:1880/krynn.pac
The PAC file itself is fine and works on all other platforms.
(2) On Windows 10 machines connected to the AD, everything -but- Chrome works to find the proxy and access the Internet.
(3)
What is the expected result?
Chrome should be smart enough to find the Proxy PAC I configured in 'Internet Settings' through GPO.
What happens instead?
Chrome on windows times out trying to access sites.
Please provide any additional information below. Attach a screenshot if
possible.
,
Jan 15
PAC file:
======================================================================
//
// $Id: krynn.pac,v 1.8 2019/01/15 21:55:11 root Exp root $
//
function FindProxyForURL(url,host) {
url = url.toLowerCase();
host = host.toLowerCase();
if (isInNet(host,"10.250.220.0","255.255.252.0") ||
isInNet(host,"127.0.0.1","255.255.255.255")) {
return "DIRECT";
}
if (shExpMatch(host, "*.lasthome.solace.krynn")) {
return "DIRECT";
}
if (shExpMatch(host, "*.ad.lasthome.solace.krynn")) {
return "DIRECT";
}
if (isPlainHostName(host)) {
return "DIRECT";
}
if (isInNet(myIpAddress(), "10.250.220.0", "255.255.252.0")) {
return "PROXY 10.250.220.254:3128";
} else {
return "DIRECT";
}
//if (url.substring(0,5) == "http:" ||
//url.substring(0,6) == "https:" ||
//url.substring(0,4) == "ftp:") {
// return "PROXY 10.250.220.254:3128; DIRECT";
//}
//return "PROXY 10.250.220.254:3128; DIRECT";
}
======================================================================
,
Jan 16
,
Jan 16
(6 days ago)
vincent.cojot@ Thanks for the issue. As this issue is related to Proxy, this is out of scope of triaging at TE end. Hence adding 'TE-NeedsTriageHelp' and requesting 'Internals>Network>Proxy' team to look into the issue and help in further triaging. Thanks.. |
|||
►
Sign in to add a comment |
|||
Comment 1 by vincent....@gmail.com
, Jan 15As an experiment, I went through the Chrome debugging procedures with --winhttp-proxy-resolver removed (chrome://net-export, Start Logging, etc..) and I noticed this in the log: {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":767,"type":24},"time":"2688571","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":431,"type":24},"time":"2691988","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":433,"type":24},"time":"2691989","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":435,"type":24},"time":"2691996","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":791,"type":24},"time":"2693509","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":810,"type":24},"time":"2693998","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":826,"type":24},"time":"2694054","type":154}, {"params":{"proxy_server":"DIRECT"},"phase":0,"source":{"id":830,"type":24},"time":"2694072","type":154}, It always says 'DIRECT'.. so it's as if Chrome didn't know how to interpret my PAC file (which works fine on other browsers). I'm attaching my PAC file here: