Re: REPORT request failed after migrating to 0.33

On Sun, 2003-11-16 at 07:59, Rodrigo B. de Oliveira wrote:

> > So the error you're seeing is that somehow mod_dav_svn has decided that
> > a GET of the root-directory of your checkout would not succeed. That's
> > a bit of a mystery, no?
> >
>
> Hmmm... What is considered the root of a checkout?

The 'root' I'm referring to has nothing to do with virtual httpd.conf
<Location>s. mod_dav_svn is validating the absolute repository path
which is the 'root' of the tree you want, e.g. something like
/projectname/trunk/

That's why I'm surprised. I mean, you're not doing any kind of
per-directory access control within your repository (with mod_authz_svn,
or whatever). So, in theory, I don't understand why you would *ever*
get read-access failure on a specific inner-repository path.

> I'm asking it because
> in the way I've set my server up the repository is accessible through the
> /boo/svn path but any path above it is actually inaccessible, in other
> words:
>
> /boo/svn - read-only by anonymous, writable by valid users
> /boo/ - access denied
> / - access denied
>
> Do you think it has something to do with it?

Naw, this is pretty standard. It's the same situation when you run our
python regression tests over http://. So it were a problem, we should
have seen it already.

There's something unique about your system, something we've never seen
before.

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