Help with setting up transparent tunnel

[Itamar O <it...@gmail.com>]

Hi all,

I am serving multiple Subversion (1.6.12) repositories with Apache (2.2)
over Windows (Server 2008).
My setup is a multi-project intranet server, so I configured it to serve all
projects using SVNParentPath
on <Location /repos> of the main company VirtualHost (on a domain e.g.
www.company.com).
This includes an authorization file for access control (path based, per
repository).

Several projects has their own domain (e.g. project.company.com),
and I'd like to allow access the project-SVN via project.company.com/repos
with minimal configuration duplication (especially the authz file).
My thought was to configure <Location /repos> on the project VirtualHost
as a "transparent tunnel" to www.company.com/repos/project,
in order to reuse all authentication and authorization configuration with no
extra effort.
I'm not an Apache expert, so I tried setting this up using ProxyPass and
ProxyPassReverse like this:
  <VirtualHost project.company.com:80>
    ProxyPass /repos http://www.company.com/repos/project
    ProxyPassReverse /repos http://www.company.com/repos/project
  </VirtualHost>
This seems to work when accessing the project domain on a web browser,
but it seems the Subversion client doesn't like this at all (I don't
remember the error message, but it fails miserably).

Any advice on how to set this up correctly?
Thanks,
- Itamar O.

Re: Help with setting up transparent tunnel

[Itamar O <it...@gmail.com>]

On Tue, Sep 21, 2010 at 9:46 PM, Itamar O <it...@gmail.com> wrote:

> Hi all,
>
> I am serving multiple Subversion (1.6.12) repositories with Apache (2.2)
> over Windows (Server 2008).
> My setup is a multi-project intranet server, so I configured it to serve
> all projects using SVNParentPath
> on <Location /repos> of the main company VirtualHost (on a domain e.g.
> www.company.com).
> This includes an authorization file for access control (path based, per
> repository).
>
> Several projects has their own domain (e.g. project.company.com),
> and I'd like to allow access the project-SVN via project.company.com/repos
> with minimal configuration duplication (especially the authz file).
> My thought was to configure <Location /repos> on the project VirtualHost
> as a "transparent tunnel" to www.company.com/repos/project,
> in order to reuse all authentication and authorization configuration with
> no extra effort.
> I'm not an Apache expert, so I tried setting this up using ProxyPass and
> ProxyPassReverse like this:
>   <VirtualHost project.company.com:80>
>     ProxyPass /repos http://www.company.com/repos/project
>     ProxyPassReverse /repos http://www.company.com/repos/project
>   </VirtualHost>
> This seems to work when accessing the project domain on a web browser,
> but it seems the Subversion client doesn't like this at all (I don't
> remember the error message, but it fails miserably).
>
> Any advice on how to set this up correctly?
> Thanks,
> - Itamar O.
>

Update:
The error message received with a WindowsSVN 1.6.11 client:
> svn ls http://project.company.com/repos/
svn: '/repos/project/!svn/vcc/default' path not found