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

Re: REPORT request failed after migrating to 0.33

From: Rodrigo B. de Oliveira <rbo_at_acm.org>
Date: 2003-11-16 14:15:26 CET

----- Original Message -----
From: "Ben Collins-Sussman" <sussman@collab.net>
To: "Rodrigo B. de Oliveira" <rbo@acm.org>
Cc: <users@subversion.tigris.org>
Sent: Sunday, November 16, 2003 12:35 AM
Subject: Re: REPORT request failed after migrating to 0.33

> On Sat, 2003-11-15 at 18:55, Rodrigo B. de Oliveira wrote:
> > I can't no longer checkout or update from a svn repository via http
after
> > migrating to the latest 0.33 revision. (file: url works fine).
> > ...
>
> Is the server running 0.33 as well? mod_dav_svn 0.33? I assume so, if
> you're getting this error when checking out from http://localhost/.
>

Yes.

> This is a new error message, being uttered by svn_repos_dir_delta (in
> libsvn_repos/delta.c:177). It means that mod_dav_svn has decided that
> you don't have permission to read the root of the tree you're trying to
> check out. Is that true? Are you using mod_authz_svn or something?
>

It shouldn't be. Apache is configured with a stock mod_auth/AuthUserFile
scheme:

 <Location /boo/svn>
   DAV svn
   SVNPath /svnroot/boo

   AuthType Basic
   AuthName "boo subversion repository"
   AuthUserFile /etc/httpd/conf/boosvn-auth-file

   <LimitExcept PROPFIND OPTIONS REPORT>
       Require valid-user
   </LimitExcept>
 </Location>

Anyways, since you told me it was an authorization related error I tried to
remove
the REPORT method from the LimitExcept directive and it started
working again. I don't understand why though...

Thanks!
Rodrigo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 16 14:15:02 2003

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

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