Thanks to all for quick and useful help.
There seemed to be two problems:
1) TortoiseSVN was storing proxy settings in a wrong location
HKEY_CURRENT_USER\Software\Tigris.org\Subversion\Servers\default
instead of
HKEY_CURRENT_USER\Software\Tigris.org\Subversion\Servers\global
(I think it should be enough to warrant a new point release)
2) Our proxy was tyoo particular about the HTTP methods it allowed through, so I had to use HTTPS and that worked like a charm :)
Thanks again all of you for the help :)
> -----Original Message-----
> From: Branko Cibej [mailto:brane@xbc.nu]
> Sent: Wednesday, May 05, 2004 7:43 PM
> To: Tepp, Roland
> Cc: users@subversion.tigris.org
> Subject: Re: subversion across strict corporate firewall
>
>
> Roland.Tepp@seb.se wrote:
>
> >Hello,
> >
> >I'm evaluating subversion as a versioning system for a small
> company that sits behind a huge and highly restrictive
> corporate firewall that does not allow anything but HTTP
> connections going out and no incoming connections whatsoever!
> >
> >I chose subversion partly because of it's promise of being
> so similar to the cvs and partly because I hoped that since
> it supports WebDAV as it's transport protocol, we could use
> it acros our firewall as WebDAV is based on HTTP.
> >
> >But alas, it seems the firewall does not allow svn requests
> to WebDAV reporitory through. (browsing of a repository with
> a web browser works just fine)
> >
> >
> This looks like you either forgot to configure proxy settings
> for your
> Subversion client, or your proxy doesn't understand the WebDAV HTTP
> extensions. This is all in the FAQ,
> http://subversion.tigris.org/project_faq.html#proxy.
>
> >I do not really know enough of networking to be 100% shure I
> know what I'm talking about, but it looks like the library,
> that svn uses to talk to WebDAV server, is using sockets to
> establish a connection to DAV server and since socket
> transport is locked in our firewall, the requests don't get
> through...
> >
> >
> *LOL*!
> Sorry...hehe...if socket transport is locked by your
> firewall, then your
> browser doesn't work either. :-)
>
> >So the big question is - what could I do (besides
> establishing HTTP tunnel to the repository server) to connect
> successfully to remote repository across firewall that does
> not allow any other connections but HTTP(S)
> >
> >
> Subversion already uses HTTP + WebDAV extensions. If your
> network uses a
> proxy, you have to configure the svn client to use it, too. If your
> proxy doesn't understand the WebDAV extensions, then you
> either have to
> get it configured so that it does, or you can maybe use HTTPS.
>
> -- Brane
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 7 13:19:17 2004