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

Error: PROPFIND of '/repos': 301 Moved Permanently

From: <mario.reissmann_at_bbraun.com>
Date: 2007-04-26 11:12:58 CEST

Hello,

I'm new to the mailing list and hope you can help me. First of all, my
configuration:

Server:
Windows 2k3
Apache 2.2.4
svn 1.4.3
mod_dav_svn and mod_authz_svn for Apache 2.2.x
mod_auth_sspi 1.0.4-2.2.2

repository: D:\SVN_REP
I created a test repository: svnadmin create -fs-type fsfs
D:\SVN_REP\testrepository

Client:
TortoiseSVN 1.4.3

svn over Apache goes well, as http://host/repos/ shows my empty
testrepository folder.

However, I cant get an empty repository on my client and import it.
This is how I tried:

empty folder -> TortoiseSVN -> Import

I tried http://host/repos/ -> Authentication -> Error: PROPFIND request
failed on '/repos' & Error: PROPFIND of '/repos': 301 Moved Permanently (
http://.....)

It's strange. The browser asks for Authentication, afterwards the box
appears again, as if I typed in a wrong password.
I type it again.. The box appears again, but the repository browser now
shows my repository. After the first try, it stayed blank.
After the third time, the box disappears, and the browser shows
Error * PROPFIND request failed on '/repos' PROPFIND of '/repos': 301
Moved Permanently (http://...).
I thought my sspi authentication didn't work, it was definitely the right
password. But results stay the same if I try basic authentication with a
passwd file or even no authentication at all.

I found my problem in the FAQ, but this couldn't solve my problem.
My web shares and repository location does not overlap, nor do I have an
object in the web root having the same name as my repository url.

Some areas of my httpd.conf:

ServerRoot "D:/Apache2.2"

DocumentRoot "D:/Apache2.2/htdocs"

<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    Satisfy all
</Directory>

<Directory "D:/Apache2.2/htdocs">
    Options Indexes FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>

<Location /repos>
DAV svn
SVNListParentPath on
SVNParentPath "D:/SVN_REP"
#SVNIndexXSLT "/svnindex.xsl"
AuthType SSPI
AuthName "Subversion-ProjectArchive"
#AuthUserFile passwd
#AuthzSVNAccessFile svnaccessfile
Require valid-user

SSPIAuth on
SSPIAuthoritative on
SSPIDomain domaincontroller.......com
SSPIOmitDomain on
SSPIUsernameCase lower
SSPIPerRequestAuth on
SSPIOfferBasic on
</Location>

This is how I disabled SSPI:

<Location /repos>
DAV svn
SVNListParentPath on
SVNParentPath "D:/SVN_REP"
#SVNIndexXSLT "/svnindex.xsl"
AuthType Basic
AuthName "Subversion-ProjectArchive"
AuthUserFile passwd
#AuthzSVNAccessFile svnaccessfile
Require valid-user
</Location>

Then, of course, I created the passwd file with the htpasswd command,
added a user and restarted Apache.
But the repobrowser behaved like beforehand. 3x Authentication & error
301.

I'm stuck... I 've been searching for two days for a solution, but it
wasn't really helpful. The TortoiseSVN mailing list said it's a subversion
problem.

Do you have any suggestions?

Kind Regards and thanks for your answers,

Mario Reissmann
********************************************************************************
The information contained in this communication is confidential, may be
attorney-client privileged, may constitute inside information, and is intended
only for the use of the addressee. It is the property of the company of the
sender of this e-mail. Unauthorized use, disclosure, or copying of this
communication or any part thereof is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by return e-mail and destroy this communication and all copies thereof,
including all attachments.
********************************************************************************
Received on Thu Apr 26 11:13:24 2007

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.