Chromium 55 does not handle .pac or .wpat proxy scripts
Reported by
spliff.r...@gmail.com,
Dec 20 2016
|
||||
Issue descriptionChrome OS Version: Chromium 55 Chrome OS Platform: Windows 7 Enterprise x64 Network info: company network, proxy through Java base .pac file We are using an application called PureCloud (v. 1.9.398) currently based on Chromium 55 (latest update) and since then the application is no longer able to interpret neither our .pac nor .wpat proxy file. Attached you will find a screenshot showing the actual log of this application with the error message. I was advised by the developer (Genesys) to report a bug with you. I am not sure if these files are sufficient. Please let me know if you require more data, I am glad to help. Regards Daniel
,
Dec 22 2016
I don't see any HOST_RESOLVER_IMPL_JOB events in that net log - the only events are 9 URL_REQUESTs to paths under chrome://resources/ and 2 UDP_SOCKETs on port 1900. Was net-internals capturing while the failed requests in that log were being made? If you load the same page that fails to load in Chrome in IE instead (since Chrome and IE use the same proxy settings), does it load there?
,
Dec 22 2016
Please load pages (that fail) while capturing is active, and attach that NetLog. According to that log, the PAC file is being used (http://wpad.fitads01.fxdir.net/wpad.dat)
,
Dec 28 2016
spliff.richards: Could you please provide the requested log? Without it, we can't make forward progress on this bug, and will have to just close the issue. Thanks!
,
Jan 2 2017
Sorry I cannot provide any logs since this is a problem not caused by Chrome browser but by a 3rd party tool called "PureCloud".
,
Jan 3 2017
,
Jan 12 2017
The application is serving web pages wrapped in a Chromium Freestanding application. Example of the application can be found https://apps.mypurecloud.com/directory-windows/ |
||||
►
Sign in to add a comment |
||||
Comment 1 by kapishnikov@chromium.org
, Dec 20 2016Labels: Needs-Feedback