On Wed, 24 Aug 2005, David Anderson wrote:
...
> Given the clarification I made above, this answers itself: a reverse
> HTTP proxy could do what I propose, for the http:// and such repository
> access methods, provided that the proxy also relays non-HTTP requests
> (DAV/DeltaV). This is already possible (I believe) by setting up a
> properly configured Apache web server, no extra design or implementation
> needed.
...
> - Add that for the http:// (mod_dav_svn) methods, a regular
> non-caching reverse HTTP proxy that is configured to relay DAV/DeltaV
> chat should (can a dav_svn guru get back to us on this?) accomplish what
> I am proposing, except for the "dynamic reconfiguration" bit which is an
> implementation detail for the svn:// proxy server software I'm
> proposing.
Hiya Dave. Having recently implemented such a DAV reverse proxy for SVN
using Apache httpd and a few key, stock modules, I can confirm that this is
possible, but does impose a number of restrictions (mostly from mod_dav),
including:
- scheme in HTTP Destination header must match (e.g. http)
- port number in HTTP Destination header must match (e.g. 80)
- URI path to repository root must match (e.g. /repos/svn)
Note that this means that just setting up mod_proxy to reverse proxy HTTP
requests is often INSUFFICIENT for a DAV reverse proxy for SVN.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 15 00:12:51 2005