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)
>
> 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...
>
> 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)
What about using HTTPS? Your firewall should not mess with the contents of
an SSL connection, should it?
And shouldn't the repository machine be inside the firewall anyway?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 5 13:47:27 2004