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

Re: Using Subversion's apache server for more than Subversion

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-09-10 06:41:33 CEST

On Mon, Sep 09, 2002 at 07:58:46PM +0200, Daniele Nicolodi wrote:
> On Mon, Sep 09, 2002 at 11:58:53AM -0400, Mike Wohlgemuth wrote:
>...
> > # turn on the rewrite engine
> > RewriteEngine on
>...
> <Location />
> ServerName svn.grinta.net
> ProxyRequests Off
> NoCache *
> ProxyPass /svn http://192.168.2.10/svn/
> </Location>
>
> in this config 192.168.2.10 is a dedicated internal SVN server but you
> can also specify http://localhost:8000/svn if you want.

Yup. ProxyPass is a *much* cleaner solution. It should also be faster and
more flexible than the rewrite-based approach.

Note that we don't have our caching headers set up properly yet, but once we
do, you *will* be able to cache the responses. And quite well, actually.
Thus, you'll most likely be able to remove the NoCache directive. It means
that your front-end server can offload a good chunk of work from your
backend SVN server. (and I seriously doubt that rewrite can do this)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 10 06:42:18 2002

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