We have a Vagrantfile that detects whether the user is on a corporate network that needs a proxy, and when so it sets config.svn_proxy.http as required. When connecting outside the corporate network, however, the proxy needs to be cleared out. At first I was attempting this in the Vagrantfile with:
But unfortunately, when the SVN proxy is configured in this way with empty proxy configs, at least in 1.7.9, it fails to connect:
svn: E175002: Unable to connect to a repository at URL 'http://core.svn.wordpress.org/trunk'
svn: E175002: OPTIONS of 'http://core.svn.wordpress.org/trunk': Could not resolve hostname `': No address associated with hostname (http://core.svn.wordpress.org)
I also tried:
config.svn_proxy.http = nil
But this had no effect on the existing SVN config (as noted in the README).
In order to restore SVN connectivity, the following command has to be run to forcibly remove the entries:
We have a
Vagrantfile
that detects whether the user is on a corporate network that needs a proxy, and when so it setsconfig.svn_proxy.http
as required. When connecting outside the corporate network, however, the proxy needs to be cleared out. At first I was attempting this in theVagrantfile
with:This would result in a
/etc/subversion/servers
that contained:But unfortunately, when the SVN proxy is configured in this way with empty proxy configs, at least in 1.7.9, it fails to connect:
I also tried:
But this had no effect on the existing SVN config (as noted in the README).
In order to restore SVN connectivity, the following command has to be run to forcibly remove the entries:
But the next time that Vagrant reloads,
vagrant-proxyconf
will restore these empty values and the manual command will have to be re-run.So when
config.svn_proxy.http
isfalse
, please have thehttp-proxy-*
SVN configs be removed entirely instead of outputting empty values.