On Feb 7, 2011, at 3:32 AM, Martin Costabel wrote: > On 6/02/11 21:17, Alexander Hansen wrote: > [] > >> Not all users _can_ use rsync, however, due to firewalls. We need to >> have a selfupdate method that works over unblocked http ports (and since >> CVS proxy support hasn't worked in a while it would be a nice change). > > Even then, although svn runs over https, someone (the famous "somebody" > Max mentioned) would need to figure out how http proxies work with svn. > And test it in real-life situations. For example, does svn respect > http-proxy-* environment variables (not mentioned in the svnbook), or > does the user have to modify their ~/.subversion/servers file?
Testing would definitely be required. :) Since sf.net only uses https for svn, there shouldn't theoretically be any problems going through a proxy. Proxies just have to let encrypted traffic through unmolested since they have no way to know what the traffic actually is. Unfortunately, it does look like you have to use ~/.subversion/servers to configure proxies though. A look at the source code confirms that. It only gets its proxy info from the servers config file. Daniel ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
