Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I can see my repository in a web browser, but svn checkout gives me an error about “301 Moved Permanently”. Whats wrong?

browser Error gives Repository web
0
Posted

I can see my repository in a web browser, but svn checkout gives me an error about “301 Moved Permanently”. Whats wrong?

0 CommentsAdd a Comment

2 Answers

0

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 , 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 does not overlap or live within any areas already exported as normal web shares.

0 CommentsAdd a Comment
0

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 , 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 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 Apac

0 CommentsAdd a Comment

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.