Closed abriceno closed 2 years ago
It looks like we'll need to add support for setting proxies for both repository resolution and for the providers themselves.
The usual Java method of setting -Dhttps.proxyHost=<host> -Dhttps.proxyport=<port>
is being ignored by HttpClient which is used by Aether (the dependency resolution library) and AWS SDK.
In #391 I added support for using the http_proxy
or https_proxy
environment variable to configure Gyro to use a proxy for fetching plugins. You may also need the updated aws provider which adds support as well.
Hello Gyro team,
For reasons of control, a proxy is now being used for outputs. At the moment, the proxy does not have content control and can connect to any site on the Internet. But, when I initialize Gyro with the proxy I get an error that it can't connect to the endpoints. I have configured the environment variables in my console: http_proxy, https_proxy, HTTP_PROXY and HTTPS_PROXY