Allow SVN through Squid Proxy :
The Subversion client can go through a proxy, if you configure it to
do so. First, edit your "servers" configuration file to indicate which
proxy to use. In Fedora core 6 the file location is
/home/sysadmin/.subversion/servers
# cd /home/sysadmin/.subversion/servers
# vi server
- - - -
- - - -
[global]
# http-proxy-exceptions = *.
exception.com,
www.internal-site.org
http-proxy-host = 192.168.1.100 (proxy ip address of your network)
http-proxy-port = 3128 (port no of squid proxy)
# http-proxy-username = defaultusername
# http-proxy-password = defaultpassword
http-compression = no
- - - - -
save the file.
Next, you need to make sure the proxy server itself supports all the
HTTP methods Subversion uses. Some proxy servers do not support these
methods by default:
PROPFIND, REPORT, MERGE, MKACTIVITY, CHECKOUT.
In general, solving this depends on the particular proxy software. For
Squid, the config (squid.conf) option is
# TAG: extension_methods
# Squid only knows about standardized HTTP request methods.
# You can add up to 20 additional "extension" methods here.
#
#Default:
# none
extension_methods REPORT MERGE MKACTIVITY CHECKOUT PROPFIND
Another technique is to attempt the checkout over SSL, which many
proxies allow:
svn checkout
https://intellimeet.googlecode.com/svn/trunk
Of course, your svn client will have to have been built with ssl
support; just pass --with-ssl to Subversion's ./configure script. You
can check to see whether the 'https' scheme is supported by running
svn --version.