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

Re: svn client issue/question

From: Peter Davis <peter_at_pdavis.cx>
Date: 2002-12-29 13:37:49 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 29 December 2002 04:37, Michael Kefeder wrote:
> why does svn list work without the
> --username option? Or are "commiting" commands treated different from
> "reading" commands in svn? If yes, why is that?

It's Apache, not Subversion, that controls access via http. Look in your
httpd.conf; mine says:

<Location /repos>
    DAV svn
    SVNPath "...."
    AuthType Basic
    AuthName "Subversion Repository"
    AuthUserFile "...../password.db"
    <LimitExcept GET PROPFIND OPTIONS REPORT>
        Require valid-user
    </LimitExcept>
</Location>

If your httpd.conf looks like that, then yes, read operations *are* different
than write operations. Read operations use the GET, PROPFIND, OPTIONS, and
REPORT http methods, and write operations use PUT and some others. So the
above httpd.conf restricts all non-read-only operations to require a valid
username authentication.

Since you are doing list and import operations on URLs without a working copy,
Subversion cannot assume a username and you must specify it with --username.
The workaround can be to either relax Apache's access controls or, um, live
with it, because that is the expected behaviour :)

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+DuyihDAgUT1yirARAlELAJ9NSAo4C0GEEBq6ZgoAjvqSyC4b4QCfQPt3
4FXK2F7dEyufi4UYxKQ98co=
=5GMM
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 29 13:38:37 2002

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