Setting to get cargo proxy info from git?

[gilescope]

cargo depends on a working git (in most cases).
git only works if the proxies are set up correctly.

Would people like / object to a cargo setting that says read git's proxy settings and use them?

Why: In a corporate env with various different proxy setups you would have a .cargo/config that would be portable between them.

At the moment it all feels not as simple as it could be to get everything up and running...
For users they typically have to set up HTTP_PROXY, .cargo/config's proxy settings and git's proxy settings before they're up and running. It would be great if we could tell cargo to just piggy back off git's proxy settings (which it depends on anyway).

Keen to hear people's thoughts.

[ehuss]

Cargo should honor the http_proxy environment setting for all network operations. I don't think Cargo would want to look at the git configuration for non-git operations, that seems like it could be confusing. Perhaps I'm misunderstanding what you are asking?

It does appear that Cargo ignores git's configuration, though. It may be as simple as setting ProxyOptions::auto, though it may be tricky to coordinate with Cargo's own proxy handling. However, even if Cargo did honor that, the user would still need to configure proxy settings for non-git operations.

[lengyijun]

Hello. I feel it necessary to set specific proxy for github.com.
In most case, we can switch crate source to somewhere near us. I can connect to my crate source without proxy.
But I also need a specific proxy to github because of some network problem.

For example, something like this in ~/.gitconfig

[http "https://github.com"]
  proxy = socks5://127.0.0.1:1080
[https "https://github.com"]
  proxy = socks5://127.0.0.1:1080