Headless chrome does not use system proxy. Regular Chrome does.
Reported by
christop...@gmail.com,
Nov 14 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Be behind a corporate proxy 2. Have Chrome configured to detect system proxy settings (this is the default on a Windows 7 install) 3. Try opening a page in regular Chrome 4. Try fetching a page with headless chrome What is the expected behavior? In regular Chrome, the page opens fine, indicating that the request has passed through the proxy as expected. In headless chrome, all requests simply time out. What went wrong? I don't know, but it seems that, when in headless mode, Chrome does not detect (and/or use) system proxy settings in the same way as when it runs in regular mode. Did this work before? No Chrome version: 62.0.3202.89 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 27.0 r0
,
Nov 19 2017
,
Jan 8 2018
In regular Chrome, proxies are handled through the preferences system, which headless does not support, so headless has it's own much simpler code path for proxies. Marking this as a feature request.
,
Jan 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by mmenke@chromium.org
, Nov 14 2017