How do I use Apache's mod_rewrite as a software load balancer without redirection for SVN?
Posted on 2010-09-15
I would like to use Apache's mod_rewrite module as a software load balancer for a number of SVN servers. My setup is like this:
team1.svn.mycompany.com = SVN server dedicated to Team #1
team2.svn.mycompany.com = SVN server dedicated to Team #2
team5.svn.mycompany.com = SVN server dedicated to Team #3
I'd like to have everyone use the same URL to access SVN. Something like this:
Depending on the repository name, I'd like an Apache instance to reroute traffic to the correct SVN server. Example:
svn.mycompany.com/repository_a reroutes to team1.svn.mycompany.com/repository_a
svn.mycompany.com/repository_b reroutes to team2.svn.mycompany.com/repository_b
I tried creating my own rewrite rules, but unfortunately, when I try to connect to the repository using TortoiseSVN or similar SVN client, I get an error message that the repository has moved temporarily. So it appears that the SVN client is detecting the redirect. I thought rewrite was supposed to avoid this.
If rewrite isn't the correct solution, can anyone offer a viable alternative?