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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Just for the record, I'm planning on leaving this intact for network servicification.  I think removing this flag should be done independently of the servicification effort, so if it turns out we need to keep it, we can, rather than rushing out a fix for broken production code not intended to support the flag with the new logic flow.

For sanity's sake, we're using the network service network setup code for in-process configuration as well as we convert things over, so we can't just break it in the new path.

This is also causing pain and suffering over on  issue 862121 . Turning this flag on breaks proxy.pac-based WebSocket proxying on both Windows and Mac.

I'd be happy if it went away, but looking at the number of blocking bugs I should probably not count on it.

Probably the only real blocking bug is  Issue 735637 , at which point I would go ahead and rename this to --deprecated-system-proxy-resolver for a release or two to see if there are any other weird dependencies.

That is useful to see from  Issue 862121  that it may be Forcepoint that is adding --winhttp-proxy-resolver! (this has been causing other problems like breaking the chrome proxy settings extension API, as --winhttp-proxy-resolver doesn't support other things like data: either)