Give CocoaPods' Downloaders the Proxy Environment

Launch pod install with HTTP proxy variables and identify whether its failing dependency download uses Git or the HTTP downloader.

For a normal HTTP proxy, supply its URL in the environment used to launch CocoaPods. In a POSIX shell, one invocation can be configured with:

http_proxy=http://proxy.example:8080 \
https_proxy=http://proxy.example:8080 \
pod install

The two variables can identify the same listener. Public-source downloads may use an address from the HTTP proxy list where that route is allowed; first check that the actual curl or Git downloader has no configured or retained proxy credentials. Their names select the destination protocols; the URL describes the proxy endpoint.

CocoaPods' HTTP downloader invokes curl, while its Git downloader invokes Git. Both receive the launch environment, but each also has its own supported configuration. A Git http.proxy entry can make that download behave differently from the HTTP downloader.

Read the dependency source and failed command in the pod output. A Git repository fetched over HTTPS follows Git's HTTP transport. An SSH source follows the SSH configuration instead.

Allakkat attuumassuteqartut