Yep, still a newbie but I'm getting closer to getting trac working in a multi-project SSL site.
I've got SSL working and user/pw on two projects. Yey! Now, I'm trying to get SVN working. First of all, I was a bit confused with the SVN part. I figured (being an SVN user and admin) that to utilize the svn repos I would need to configure the directives in the httpd.conf (or subversion.conf) config file. But, it looks like trac takes care of all that. Please tell me that I've guessed right here ;-) Here's my next hurdle: When I try to access project1 in a web browser: https://my.domain.com/project1 The certificate pops up (my test cert) and once I accept the cert, the user/pw challenge pops up. I can log on and I am given access to all features of project1. Trac it works fine here. HOWEVER, accessing thru svn and selecting to accept the certificate permanently when doing this: svn checkout --username myname --password mypwd https://my.domain.com/project1 project1_local I get the following error: svn: PROPFIND request failed on '/project1' svn: PROPFIND of '/project1': 301 Moved Permanently (https://my.domain.com) I googled on this and found several reports that 301 error occurs also because of other errors (like not having a 404 error page for apache). But, since trac sees the SVN repo fine, why doesn't svn? So, anyone seen this error and know where I could look? brad _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
