Chrome's builtin help>check update can not use network proxy configured by SwitchySharp extension
Reported by
ctengc...@gmail.com,
Feb 8 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Install `SwitchySharp` extension and configure a bypass-gfw http(s) proxy 2. Open help > about chrome > check update 3. What is the expected behavior? Chrome's builtin help>check update should be able to use network proxy configured by SwitchySharp extension What went wrong? check update can only use system proxy. Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 24.0 r0
,
Feb 8 2017
****Bulk Edit**** Setting as P1 for test team to prioritize in triaging.
,
Feb 9 2017
,
Feb 9 2017
Tested the issue on Mac 10.12.2 (Non-corp machine) using chrome reported version #56.0.2924.87. Attached a screencast for reference. Steps followed to reproduce the issue are as follows: ----------- 1. Added SwitchySharp extension and configured a bypass-gfw http(s) proxy. 2. Opened help > about chrome > checked update. 3. No system proxy was used while checking update. Could anyone from Network>Proxy team please help us in triaging the issue further. Hence, adding TE-NeedsTriageHelp label for further investigation. Thanks...!!
,
Feb 9 2017
Note: my local network is inside GFW, so cannot access chrome's update, if your local network is directly access to goole sites, then you can just deploy a localhost http proxy server script, and config it in SwitchySharp extension. If chrome's update uses this proxy, you can see the log in proxy scripts. This problem is not very severe, it's just not flexable. Although config system network proxy is usable, but it will affect all the local apps.
,
Feb 10 2017
Updating is handled by a separate application. I imagine this is a WontFix, as it is unclear what this would mean. * Chrome can have multiple profiles with separate proxy settings, which one would the updater use? * Assuming you choose some default profile, this would mean that in order to update Chrome it would be necessary to actually run Chrome and run some profile's extensions, in order to determine the proxy settings. That sort of cyclic dependency would IMO be bad.
,
Feb 11 2017
But i thought this should not be WonFix, because: 1、This is a usability problem, not "Intent by Design". if i need the update to use the system proxy, i have to set the system's one, which will cost more time. If use extension, i can simple click to switch. 2、Also the chrome update should be perceivable to any network proxy config change, if there is multiple configs, it can iterate over them until finding a usable one. 2017-02-11 4:37 GMT+08:00 ero… via monorail < monorail+v2.2202454187@chromium.org>:
,
Feb 13 2017
Chrome extensions don't affect the installer. This is working as intended. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by csharrison@chromium.org
, Feb 8 2017