Geoff Field <geoff_fi...@aapl.com.au> writes: >> When I try to reproduce the problem I get a HEAD request that >> generates >> "404 not found" rather than "401 unauthorized". What sort of >> authentication have you configured? Are you using path-based authz? > > Here's what I think is the relevant section of our httpd.conf: > > <Location /Subversion> > DAV svn > SVNParentPath L:/Subversion/Repositories > SVNAutoversioning on > > AuthType SSPI > AuthName "Subversion repositories" > Require valid-user > SSPIAuth On > SSPIAuthoritative On > SSPIDomain AAPL > SSPIOfferBasic On > SSLRequireSSL > # SSPIUsernameCase lower ## Breaks authentication > # SSPIPerRequestAuth Off ## This breaks Apache2 > > AuthzSVNAccessFile L:\Subversion\conf\svnaccessfile.conf > > Note that we're running Apache 2.0. Here are the exact details from > the server's "Services" applet:
If you could disable AuthzSVNAccessFile, or move the test repository to another Location that doesn't have authz, and then try the commit we could determine whether Subversion's authz is the problem. The apache error log may also have some relevant information about the 401. I don't have an Apache 2.0 build to test so I can't determine whether the problem is related to using 2.0. Perhaps something in 2.0 is causing the 401 instead of a 404. -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data
