Support DHCP-based WPAD on Mac |
||||
Issue descriptionDHCP based WPAD is supported on Chrome for Chrome OS and Chrome for Windows, but not other platforms. A user report received sent to me over email suggested that Mac OS supports DHCP for proxy auto-detect, making this a more noticeable ommission on Mac. I have not confirmed this (bug investigator should check which versions of macOS supports this). Based on their data, the resolution is happening at the settings layer. So for instance when you run "scutil --proxy" you get a "ProxyAutoConfigURLString" key that contains the URL fetched for auto-detect rather than that set via the network control panel. The consequence is that when using Chrome in the default mode (using system proxy settings) things work as expected. However if you configured Chrome to use "auto-detect" pushed via Policy, then it fails to detect the same URL as Chrome's (mac) WPAD does not do DHCP.
,
Nov 2
,
Nov 5
Hrm, it seems that if this is really supported on the OS level, it would probably be enough to document this properly. Or would we consider implementing our own dhcp_pac_file_fetcher_mac ? For future reference, the policy that's being talked about is ProxyMode[1]. IIUC, the following settings will have the following effect on a Mac OS device which presumably resolves DHCP-provided PAC scripts on the system settings level: "auto_detect" = Auto detect proxy settings --> This will NOT respect the PAC script because chrome on Mac does not have a DHCP-based WPAD implementation "system" = Use system proxy settings --> This would respect the PAC script because it's supposedly in the system settings (not set) --> If the user doesn't configure anything, we probably default to system. "direct", "pac_script","fixed_servers" behave as expected [1] https://sites.google.com/a/chromium.org/dev/administrators/policy-list-3?pli=1#ProxyMode
,
Nov 5
If macOS supports it, we should too for consistency. Otherwise it is unexpected that simply changing where settings are pulled from (auto-detect from OS settings, vs auto-detect pushed via policy) results in different PAC scripts being used.
,
Nov 19
Thanks! I think this would be a Feature Request from our perspective then. Do you know who would be the right person to drive the prioritization of this?
,
Nov 21
The first step is to confirm that macOS supports DHCP-WPAD in the same manner as WinInet does SmartWPAD. But given there have been bug reports, it seems likely that is the problem.
,
Dec 5
Hey, this has been Untriaged since Nov 2. @eroman, assigning to you since you're both the filer and last commenter to ensure it has an owner |
||||
►
Sign in to add a comment |
||||
Comment 1 by igorcov@chromium.org
, Nov 2Status: Duplicate (was: Untriaged)