Hi Bakki,
why do you have just one authz file? I do have one for
every repository. Much better to keep them completely
seperated. If you don't want to keep them seperated you are
better off having just one repository and 2 folders on your
root path (/mycompany,/clients).
However, if you do have 2 repositories it's better to have
one authz file for every one. Where is your file located?
Normally the repository itself has an human readable file
structure with a /conf folder. There's your authz file
for the current repository you should customize.
That's how it works for me. Maybe there's a problem with
one authz file for 2 repos, I don't know about.
But why do you think about removing the acl file? having
no access control? I'd advise you not to do it, but it's
up to you ;-)
Hope I could be of any help...
regards
clemens
PS: if you reply, try to reply to the mailing list too,
so everybody can follow our conversation
> -----Original Message-----
> From: Bakki Kudva [mailto:bakki.kudva@gmail.com]
> Sent: Freitag, 09. März 2007 15:04
> To: c.mensik@ipsquare.at
> Subject: Re: 403 forbidden error
>
> Hi Clemens,
>
> Thank you for responding. First of all I was mistaken about the repos.
> I had forgotten that I did indeed create two seperate repos.
>
> /home/svn/mycompnay
> /home/svn/clients
>
> The dav_svn.authz file looks like:
>
> # svn access control
> [mycompany:/]
> bakki = rw
>
> [clients:/]
> bakki = rw
> client = r
>
> Here is the interesting part in the apache error.log [Thu Mar
> 08 15:24:10 2007] [error] [client 1.2.3.4] Access denied:
> 'bakki' PROPFIND projects:/ror/sr/trunk
> [Thu Mar 08 15:46:10 2007] [error] [client 1.2.3.4] The URI
> does not contain the name of a repository. [403, #190001]
>
> This means instead of using mycompnay: as the repo name it is using
> projects: which is below mycomany:
>
> I got this error even after checking out a copy and then
> checking it back in.
>
> After reading "Do you really need path-based access control?"
> in the svnbook I am thinking of removing acl altogether.
>
> If I remove the directive from the dav_svn.conf and don't
> load authz module will there be any other side effects?
>
> What do you think is going on and do you think removing authz
> would be a good solution?
>
> THanks,
>
> bakki
>
>
> On 3/8/07, Clemens Mensik <c.mensik@ipsquare.at> wrote:
> > Hi,
> >
> > on the first hand everything seems to look fine. But maybe you've
> > misconfigured your acl. How does it look like?
> > Also try to look into your apache log: what does it tell you?
> >
> > regards
> > clemens
> >
> > > -----Original Message-----
> > > From: Bakki Kudva [mailto:bakki.kudva@gmail.com]
> > > Sent: Donnerstag, 08. März 2007 23:07
> > > To: subversion users
> > > Subject: 403 forbidden error
> > >
> > > Hi all,
> > >
> > > I have a repo at /home/svn. It used to contain only
> projects of my
> > > company such as /svn/projects/this/or/that
> > >
> > > I decided to use the same repo for projects I develop for
> clients so
> > > split it like so. (not two repos but two paths in one)
> > >
> > > /svn/mycompnay/projects/this/or/that
> > > /svn/clientcompany/paying/projects
> > >
> > > The clientcompany side works fine but one of my company projects
> > > which was dormant for a while gives me errors. I thought
> it might be
> > > because it may have been checked out pre-split, so I did a svn co
> > > (which works
> > > fine) to a new working copy applied the new changes and tried to
> > > commit but I get..
> > >
> > > svn: Commit failed (details follow):
> > > svn: OPTIONS request failed on '/svn'
> > > svn: OPTIONS of '/svn': 403 Forbidden (http://mycompany.com)
> > >
> > > I have setup only basic auth and am using dav_svn module. I
> > > generated the passwords to /etc/apache2/dav_svn.passwd I am using
> > > dav_svn.authz to specify which user has r / w rights.
> > >
> > > Some excerpts from the dav_svn.conf...
> > > <Location /svn>
> > >
> > > DAV svn
> > >
> > > # Set this to the path to your repository
> > > SVNParentPath /home/svn
> > >
> > > # Uncomment the following 3 lines to enable Basic Authentication
> > > AuthType Basic
> > > AuthName "Subversion Repository"
> > > AuthUserFile /etc/apache2/dav_svn.passwd
> > >
> > > # Uncomment the following line to enable Authz Authentication
> > > AuthzSVNAccessFile /etc/apache2/dav_svn.authz
> > >
> > > # The following three lines allow anonymous read, but make
> > > # committers authenticate themselves.
> > >
> > > # <LimitExcept GET PROPFIND OPTIONS REPORT>
> > > Require valid-user
> > > # </LimitExcept>
> > >
> > > </Location>
> > >
> > > Any ideas why commits fail?
> > >
> > > TIA,
> > >
> > > bakki
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > > For additional commands, e-mail: users-help@subversion.tigris.org
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 11 16:45:34 2007