Issue metadata
Sign in to add a comment
|
Chrome picks some long-unused proxy setting from system until internet explorer is opened.
Reported by
jbenn...@birkdalehigh.co.uk,
Jan 5 2017
|
||||||||||||||||||||||||
Issue description
Chrome Version : 55.0.2883.87 (Official Build) m (64-bit)
Other browsers tested:
Safari:
Firefox:
IE: OK
What steps will reproduce the problem?
(1) Some domain user tried to load a page
(2) They get no connection
(3) open internet explorer, the home page loads immediately
(4) close IE
(5) refresh anything in chrome, it now loads
What is the expected result?
load pages the first time with the system proxy, which is set to DIRECT.
What happens instead?
Chrome found some proxy setting not used for 12 months, that isn't in any GPO for 12 months and has never need applied to this computer image that was installed recently.
Please provide any additional information below. Attach a screenshot if
possible.
chrome://policies proxy setting is set to SYSTEM, correct.
watching the page chrome://net-internals/#proxy shows the old 10.201...:8080 proxy address. This changes to SYSTEM Direct the second IE starts running.
the only thing that could be left over is the user mandatory profiles on on the domain haven't been updated in a long time.
This has only become an issues since I've changed the chrome GPO from "Direct access" itself to "use system"
Again this system is a pretty fresh install, it has never had proxy settings entered into it at all.
,
Jan 6 2017
Thanks for the report. What version of Windows are you using? Chrome uses WinHttpGetIEProxyConfigForCurrentUser() to determine the proxy settings, which doesn't seem to be working properly. Short of Microsoft fixing WinHttpGetIEProxyConfigForCurrentUser(), the best solution is probably to tackle https://bugs.chromium.org/p/chromium/issues/detail?id=118385 and use WinInet to access the settings instead, as that mechanism has better support. I am pretty sure this is another instance of WinInet vs WinHttp, however if you would like to confirm you can try running the binary from this bug thread: https://bugs.chromium.org/p/chromium/issues/detail?id=12189#c54
,
Jan 10 2017
jbennett@ could you please respond to the comment #2.
,
Jan 13 2017
Doh error reporting 101, sorry. What version of Windows are you using?: Windows 7 x64 Enterprise. I had to wait for a low usage time as I couldn't get any test policy to reproduce it. Changing the work around from chromes "Never use a proxy" back to "Use System" and it breaks again, file attached. I rebooted the computer and did the same again, same result.
,
Jan 20 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Jan 6 2017Labels: Needs-Triage-M55