Dealing with SVN PROPFIND failed - 301 Moved Permanently error

Tagged:  

svn: PROPFIND request failed on '/projectpath'
svn: PROPFIND of '/projectpath': 301 Moved Permanently

It means your httpd.conf is misconfigured. Usually this error happens when you've defined the Subversion virtual "location" to exist within two different scopes at the same time.

For example, if you've exported a repository as <Location /www/foo>, but you've also set your DocumentRoot to be /www, then you're in trouble. When the request comes in for /www/foo/bar, apache doesn't know whether to find a real file named /foo/bar within your DocumentRoot, or whether to ask mod_dav_svn to fetch a file /bar from the /www/foo repository. Usually the former case wins, and hence the "Moved Permanently" error.

The solution is to make sure your repository <Location> does not overlap or live within any areas already exported as normal web shares.

It's also possible that you have an object in the web root which has the same name as your repository URL. For example, imagine your web server's document root is /var/www and your Subversion repository is located at /home/svn/repo. You then configure Apache to serve the repository at http://localhost/myrepo. If you then create the directory /var/www/myrepo/ this will cause a 301 error to occur.

Source: http://subversion.tigris.org/faq.html#http-301-error
Please notify for broken or misleading link - Thank You
 

P.S. It seems like many people are facing this problem. I apologize for any inconvenience for forwarding you to different site, rather than just explaining here.

 

© Hossain Khan - Some rights reserved.
Creative Commons License This site is licensed under a Creative Commons Attribution-Noncommercial 2.5 License.