Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat empty proxy settings as a signal to _not_ use a proxy #449

Merged
merged 1 commit into from
Sep 13, 2021

Conversation

mjcheetham
Copy link
Collaborator

When proxy settings are set in Git, an empty value is treated as "do not use a proxy". We update GCM to do the same thing; when an empty value is set, we do not use a proxy.

This allows for the scenario where a proxy has been set globally (unscoped) but a specific (scoped) remote does NOT have a proxy set.

Fixes #442

When proxy settings are set in Git, an empty value is treated as "do
not use a proxy". We update GCM to do the same thing; when an empty
value is set, we do not use a proxy.

This allows for the scenario where a proxy has been set globally
(unscoped) but a specific (scoped) remote does NOT have a proxy set.
@mjcheetham mjcheetham merged commit e0de41b into git-ecosystem:main Sep 13, 2021
@mjcheetham mjcheetham deleted the proxy-noproxy branch September 13, 2021 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Empty proxy for scoped section not respected when proxy is set for unscoped
3 participants