On Apr 22, 2014, at 17:00, Tom Kielty wrote: > We have been using SVN with WebSVN for 7 years now. It is a non-SSL, hosted > on a Windows 2008 R2 server behind Apache 2.2. > > Recently we looked into upgrading from SVN 1.7.5 with WebSVN 2.3.3 to SVN > 1.8.8 and the same WebSVN 2.3.3. > > The SVN upgrade worked with no issues. > I ran the svnadmin upgrade <repo_path> step with no issues. > > However, when I replaced the mod_dav_svn.so and mod_auth_sv.so with the > latest versions my WebSVN stopped working. The clients work fine for > accessing the server. And the direct URL http://<server>/RND work correctly > as well. > > However, WebSVN does not. If I do not replace the modules WebSVN continues to > work just fine. When I do replace them I get a "Not Found" error when going > to http://<server>/websvn/index.php. If I just go to http://<server>/websvn I > get my main repo listing. Before I would get the files under the websvn > folder in apache. > > I figure I am missing something that changed form 1.7 to 1.8 but I can't > pinpoint it. Below are my <Location> definitions from my http.conf file. > > <Location /RND> > DAV svn > SVNPath D:/Repositories/RND > AuthName "SVN Server" > AuthType SSPI > SSPIAuth On > SSPIAuthoritative On > SSPIDomain <mydomain> > SSPIOfferBasic on #let non-IE clients authenticate > SSPIOmitDomain On > AuthzSVNAccessFile "D:/Repositories/RND/svnaccess.conf" > Require valid-user > </Location> > > <Location /websvn/> > SVNPath D:\Repositories\RND > AuthType SSPI > SSPIAuth On > SSPIAuthoritative On > SSPIDomain <mydomain> > SSPIOfferBasic On > SSPIOmitDomain On > Require valid-user > </Location> > > Any suggestions would be appreciated.
You shouldn’t be setting SVNPath within the “<Location /websvn/>” block, should you? That only belongs in the “<Location /RND>” block. Consult your Apache error log for information on why an error occurred.
