You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.
When connecting to https://chocolatey.org/api/v2/, the chocolatey client (v0.9.9.11) correctly uses the configured proxy server (configured via choco config set proxy). However, when connecting to nuget servers on my local LAN segment, the proxy settings are seemingly ignored and the client attempts to connect directly.
Often times a corporate proxy is still required to access a local web/NuGet server. Could you please consider making proxy bypass configurable?
The issue persists when using an IPv4 address, hostname or FQDN of a local NuGet host.
I've confirmed this issue in WireShark and Fiddler.
When connecting to https://chocolatey.org/api/v2/, the chocolatey client (v0.9.9.11) correctly uses the configured proxy server (configured via
choco config set proxy
). However, when connecting to nuget servers on my local LAN segment, the proxy settings are seemingly ignored and the client attempts to connect directly.Often times a corporate proxy is still required to access a local web/NuGet server. Could you please consider making proxy bypass configurable?
The issue persists when using an IPv4 address, hostname or FQDN of a local NuGet host.
I've confirmed this issue in WireShark and Fiddler.
Running in PowerShell on Windows 10
The text was updated successfully, but these errors were encountered: