Allow marking PAC (proxy auto-config) as mandatory via Chrome Policy |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.209 Safari/537.36 Steps to reproduce the problem: 1. PAC file failed to be fetched/downloaded 2. Device connects to DIRECT connection What is the expected behavior? Device should not connect to DIRECT connection when PAC failed What went wrong? n/a Did this work before? N/A Chrome version: 58.0.3029.81 Channel: stable OS Version: 10323.67.0 Flash Version: 29.0.0.140
,
Apr 20 2018
eroman will know more, but we already do support this. If the PAC is marked as mandatory (by policy, I believe?), we don't fall back to direct on error.
,
Apr 20 2018
Comment #2 is correct. When using the system integration for proxy settings, the behavior is as noted in comment #0: a failure fetching the PAC script falls back to DIRECT per the normal interpretation of proxy settings. One can change this behavior by instead setting the proxy settings via the extension API (https://developer.chrome.com/extensions/proxy). When setting it from this location you can set mandatory=true. This will make a failure fetching the PAC script unrecoverable.
,
Apr 23 2018
Hi, I am at the origin of this request for change. The solution described in Comment #3 does not answer to my need because I am forced to develop/use an extension in order to configure the Chrome proxy with the API. I wish I could do this natively with a Chrome policy. Bests regards, M. Francois BOYER.
,
Apr 23 2018
Re-opening as a feature request for Chrome Policy option then.
,
Apr 24 2018
,
May 2 2018
Updates?
,
Aug 1
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by csharrison@chromium.org
, Apr 20 2018