Re: 404 on CHECKOUT

Following up on my own post...

> I recently changed my Apache configuration from using an Apache Limit to
> AuthzSVNAccess file, and something seems to have broken. When I try to
> commit I now get a 404 response.

I've looked at the mod_authz_svn code, and there is a changelog entry
where the response code for "unauthorised" was changed from "401
Unauthorised" to "404 Not Found". I don't know why, but I'm prepared to
believe it is the right thing to do. It sent me down the wrong track
though... My problem was permissions-related after all.

> 62.253.128.12 - - [31/Oct/2005:14:01:43 +0000] "MKACTIVITY
> /!svn/act/d25cf719-6d04-0410-a516-93fa8b957e6f HTTP/1.1" 201 290 "-"
> "SVN/1.2.3 (r15833) neon/0.24.7"

I'm a bit suprised that the MKACTIVITY was allowed anonymously;
shouldn't it need write access?

> /etc/svnaccess.conf includes
>
> [/]
> phil = rw
>
> [/anyterm]
> * = r

OK, here's the problem. It seems that "*=r" removes the w permission
that I gave myself globally. That isn't what I was expecting. It seems
that I have to add write permission back explicitly:

[/]
phil = rw

[/anyterm]
* = r
phil = rw

So the problem is solved. But is this really the most reasonable
semantics for the access file? And wouldn't it be better for the the
client to report "permission deined", rather than asking for a new
username and password?

Cheers,

--Phil.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 1 00:25:51 2005