Issue metadata
Sign in to add a comment
|
WPAD configuration is not taking effect
Reported by
ma.vanbr...@crestec.nl,
Sep 19
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Setup DHCP server with option 252 2. Setup a web server to publish the *.pac script 3. Setup the GPO: Google/Google Chrome/Proxy server > Use system proxy settings 4. Configure the proxy auto configuration via GPO 5. Verify that proxy settings are being applied (Windows 10 desktop) Google Chrome does not use the proxy server in the auto-configuration mode whereas Internet Explorer 11 does. What is the expected behavior? Google Chrome should use the Proxy Pac script to redirect traffic to the internal proxy server What went wrong? Google Chrome connects directly to the Internet bypassing the proxy. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version: This only occurs with Auto-configuration, if the proxy is explicit defined it works as expected.
,
Sep 19
,
Oct 1
I have the same problem. When I run chrome with -winhttp-proxy-resolver it works.
,
Oct 1
In screenshot #0 the URL that was auto-discovered is blacked out. Is it the same URL you set from DHCP? If you enter the URL directly as the custom PAC URL rather than using WPAD does it behave differently? Assuming the auto-discovered URL is the same, the issue could be PAC execution. Are you using any of the Microsoft specific PAC extensions? (i.e. *Ex() functions).
,
Oct 2
Or is the PAC script making use of myIpAddress() or myIpAddressEx()? This is broken in Chrome ( Issue 735637 )
,
Oct 2
#4: The proxy pac URL is the same in the DHCP and the Internet Options #5: Thanks for the heads up, our proxy pac does make use of myIpAddress() as soon as I updated the script to always return the proxy my issue has been solved.
,
Oct 2
#5: In my case I use an array to white list and a for loop to return "DIRECT" when the host is in the array and when it is not return the proxy variable. It stopped working after upgrading to version 69.
,
Oct 2
Thanks for the feedback! The original reporter's issue (ma.vanbreet) is a duplicate of 735637. #7: Please first confirm that chrome://net-internals#proxy shows you PAC script is being used (it should show the expected PAC URL). If it is, then please attach your PAC script and I can take a look why it executes differently.
,
Oct 2
#9: That means the PAC file is not being used - either because it failed to be downloaded, or the file downloaded could not be parsed as JS. The file itself looks fine, so it is probably an issue fetching it. Please capture a Net Log by following these instructions: https://www.chromium.org/for-testers/providing-network-details In particular, once you have started capturing, click the "Re-apply settings" on chrome://net-internals#proxy so the trace will include the fetching of the PAC file.
,
Oct 2
@eroman, thanks for the help. Follows log file.
,
Oct 2
#9, #11: Thanks for the extra data! I believe I know the problem, and will follow-up with you via Issue 891526 .
,
Oct 2
ma.vanbreet's bug --> Duped of Issue 735637 gabrielfn's bug --> New issue, tracking with Issue 891526 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by atwilson@chromium.org
, Sep 19