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

Virtual host with PROPFIND 301 problem only on top level repos

From: Stephan A. Rickauer <stephan_at_ini.phys.ethz.ch>
Date: 2005-04-13 12:46:57 CEST

Guys, I spent the whole day searching infos for my problem on the web
and could not resolve my issue. My last hope is you :) Maybe you can help.

It sounds pretty easy:
A working svn setup under https://svn.example.com, virtual ssl host with

Several repositories are hosted under /www/rcs/svn, e.g. 'it'

Now: Working on all top-level repositories will fail with the well known

   svn: PROPFIND request failed on '/it'
   svn: PROPFIND of '/it': 301 Moved Permanently (https://svn.example.com)

BUT: Working *within* a subdirectory like 'it/something' would work.

Here is the relevant part of the configuration:

<VirtualHost MY-IP-HERE:443>
ServerName svn.example.com
DocumentRoot /srv/rcs/svn

<Location />
     DAV svn
     SVNParentPath /srv/rcs/svn
     AuthzSVNAccessFile /etc/apache2/svn_auth.conf
     AuthType Basic
     AuthName "Subversion Repository"
     AuthUserFile /etc/svn.passwd
     Require valid-user


Of course I tried various combinations of other settings for
DocumentRoot, SNVParentPath etc. But all I achieved is worse than now,
where people can at least work on the subdirectories of their repositories.

Any help is greatly appreciated. Let me know if you need more infos ...

Stephan A. Rickauer
Institut für Neuroinformatik
Universität / ETH Zürich
Winterthurerstr. 190
CH-8057 Zürich
Tel: +41 44 635 30 50
Sek: +41 44 635 30 52
Fax: +41 44 635 30 53
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 13 12:53:05 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.