[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Protocol proxy?

From: Monks, Peter <peter.monks_at_vignette.com>
Date: 2005-01-06 00:42:03 CET

G'day again,

Martin made the (in hindsight obvious!) suggestion to configure
https:// access on the internal server (in addition to the existing
svn:// access method) and then just forward port 443 through the
firewall. That way internal people can continue accessing it via
svn:// and external people can access it via https://.

As far as I can tell that would handle our case beautifully and would
be a lot simpler than trying to convert protocols (https:// to svn://)
on the fly via some kind of proxy process.

I guess the only complication is getting the configuration correct so
that having the multiple access methods on the internal server doesn't
hose the repository. That doesn't bother me too much, since it's a
topic that's received a fair bit of attention on this list.

Cheers,
Peter
 
----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
pmonks_at_sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------
 

 
 

> -----Original Message-----
> From: Monks, Peter
> Sent: Wednesday, January 05, 2005 2:44pm
> To: users@subversion.tigris.org
> Subject: Protocol proxy?
>
> G'day everyone,
>
> I was just wondering whether anyone knows of, or has implemented a
> "protocol proxy" for Subversion?
>
> What I'm envisaging is an equivalent of the SVN Apache plugin that
> instead of operating on a local repository, would proxy all requests
> on to a repository that is located elsewhere and is served by either
> the svn://, http:// or https:// protocols.
>
> The use case is that we have an existing Subversion repository housed
> on a server inside the firewall that we wish to make accessible
> outside the firewall. However for a variety of reasons we are unable
> to expose the server directly - instead I was hoping to configure some
> kind of proxy outside the firewall that would forward all requests
> to the internal server.
>
> In this specific instance the internal server is accessible via the
> svn:// protocol and we'd like to configure the external proxy to use
> https://, but I'm thinking that other combinations would also be
> useful.
>
> Is such a thing possible? If so, does anyone know where I might find
> such a beast?
>
> Thanks!
> Peter
>
> ----------------------------------------------------------------------
> Peter Monks http://www.sydneyclimbing.com/
> pmonks_at_sydneyclimbing.com http://www.geocities.com/yosemite/4455/
> --------------------------------------------------------------
> --------
>
>
> ---------------------------------------------------------------------
> 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 Thu Jan 6 00:44:23 2005

This is an archived mail posted to the Subversion Users mailing list.