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

Re: "svn lock" crash against certain 1.1.x servers

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-08-12 14:15:01 CEST

Philip Martin wrote:

>Justin Erenkrantz <justin@erenkrantz.com> writes:
>>On Fri, Aug 12, 2005 at 05:18:04AM +0200, Branko ?ibej wrote:
>>>I don't think we can do anything about the repeated authn prompts --
>>>IMHO they're caused by a server bug. I verified that this doesn't happen
>>>with httpd-2.0.54/svn-1.1.1 on Windows, and IIRC Philip verified
>>>httpd-2.0.54/svn-1.1.4 on *nix.
>>Nothing particularly jumps out at me that would have changed between httpd
>>2.0.50 and 2.0.54 that would affect this. -- justin
>It's possible the different behaviour is due to a different auth setup
>between the tsvn server and my server. I used httpd to require
>read/write auth for all access, tsvn uses mod_auth_svn and probably
>allows read-only access as well as read/write access.
D'you know, I think you're right! The damn mod_authz_svn takes it upon
itself to return HTTP_UNAUTHORIZED in the auth_checker hook, even though
it's thecking authorization, not authentication. I think this is a bug
in mod_authz_svn. It should be returning HTTP_FORBIDDEN (as in the
access_checker hook), and probably shouldn't provide an auth checker at all.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 12 14:17:18 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.