New issue
Advanced search Search tips

Issue 709997 link

Starred by 2 users
Status: Assigned
Owner:
eroman@chromium.org
Cc:
huanzhong@chromium.org
rhalavati@chromium.org
marchuk@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Mac OS system proxy not recognized while user logged into Chrome Browser.

Project Member Reported by gonzalezjo@google.com, Apr 10 2017 
Chrome Version: 57.0.2987.133 Stable, 58.0.3029.41 Beta, 59.0.3060.0 Canary
OS: MacOS Sierra 10.12

What steps will reproduce the problem?
(1) Configure a Proxy at OS level in Mac OS network settings.
(2) In the Admin Console, configure the ‘Proxy Mode’ policy in User Settings to ‘Always auto-detect the Proxy’
(3) Log in to Chrome Browser with a User located in the Org Unit where this policy was set.
(4) Check Net-Internals Proxy settings, and the effective proxy settings are set to ‘Use DIRECT connections’, while the original proxy settings are set to ‘Auto-detect’

What is the expected result?
Chrome Browser should recognize the proxy settings set at OS level.

What happens instead?
Chrome Browser does not recognize proxy and goes ‘Direct’

Additional Information:

-If the users are not logged in to Chrome, the browser recognizes the proxy configuration and the ‘effective proxy settings’ are the ones configured at OS level.
-This can be reproduced in Mac OS only.
-Same user is able to log into Chrome Browser in windows, with the same policies and same proxy configuration and the ‘effective proxy settings’ show the one set at the OS level.

Link to Drive folder containing Net internals (Google Restricted):
https://drive.google.com/open?id=0B0AAlIHNGkIybmRqa3JELWdkOWc

Similar bug reports.
 crbug.com/685328 . In the bug the customer reports the issue happens in Windows, in the bug I opened, the issue happens in Mac OS.

Comment 1 by eroman@chromium.org, Apr 10 2017 

Note that the Mac system settings are not the same as the settings you configured through Admin Console.

The System settings are:

  Auto-detect
  PAC script: http://XXX

Whereas the signed in settings are:

  Auto-detect

In particular, the system settings include an explicit PAC script (which I have elided to http://XXX).


Now, your data shows that on Windows "Auto-detect" is sufficient to infer http://XXX, whereas on Mac auto-detect does not resolve to http://XXX.

The reason for this is most likely that the WPAD is being done over DHCP -- Windows Chrome supports DHCP-based discovery of PAC scripts, whereas Mac Chrome only supports DNS-based discovery of PAC scripts.

So your solutions are to either:

(1) Advertise WPAD on the network using DNS as well (i.e. serve a PAC script off of http://wpad/wpad.dat)
(2) Change the settings in the admin console to configure a URL-based PAC script: http://XXX

If you want to confirm whether WPAD is in fact being done via DHCP, then go to chrome://net-internals/#proxy, click the "Re-apply settings" button, and then attach the resulting log (do this for both a working instance of Chrome, and a failing one).

Comment 2 by marchuk@chromium.org, Apr 10 2017

Cc: marchuk@google.com
Labels: Hotlist-Enterprise

Comment 3 by dullweber@chromium.org, Apr 11 2017

Components: Privacy
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 20 2017

Labels: Hotlist-Google

Comment 5 by rhalavati@chromium.org, Oct 29

Cc: -marchuk@google.com rhalavati@chromium.org marc...@google.comm
Components: -Privacy
eroman@,

Does your comment mean this is working as intended and can be closed?
Do we need to update help pages to prevent the confusion?

Comment 6 by eroman@chromium.org, Oct 29

Labels: Needs-Feedback
This is probably a duplicate of 897941.

I haven't had time to setup and test DHCP on Mac, but the hypothesis is that Mac does DHCP WPAD under the hood and inserts the resolved URL into the proxy settings it hands out. Which means when using "auto detect" in Chrome settings, vs using "auto detect" from system settings, you get different results.

Comment 7 by rhalavati@chromium.org, Oct 30

Cc: huanzhong@chromium.org
Thank you eroman@ for the feedback.

huanzhong@,
Could you please follow this up and check if the hypothesis is correct and we can merge it with 897941?

Comment 8 by b...@chromium.org, Nov 15 

Ping huanzhong: please follow-up as requested in comment #7.  Thank you.

Comment 9 Deleted

Comment 10 by huanzhong@chromium.org, Nov 16 

eroman@,

We have difficulties reproducing the bug (not having an administrator account to sign in to Admin console) and also verifying the hypothesis you made. Can we ask for your support on approaching these?

Comment 11 by mmenke@chromium.org, Dec 5

Cc: -marc...@google.comm marchuk@google.com
Labels: -Needs-Feedback
Owner: eroman@chromium.org
Status: Assigned (was: Untriaged)
[eroman]:  Assigning this to you to follow up on, when you get back into the office.
►

Sign in to add a comment