--On Sonntag, 29. Dezember 2002 04:37 -0800 Peter Davis <firstname.lastname@example.org>
> 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
> 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.
I know that - i have similar settings for http, to have anonymous access to
other repositories, but my https config says
AuthName "repos private"
Require group private
now when i run
svn list https://svn.home/repos
I get asked for the password of the logged in user and then for
username/password - and it works. But import doesn't, that is what confused
me. That special repository "repos" has no anonymous http access (there
isn't even an entry in httpd.conf) because it contains the history of the
server setup, nothing anybody else but the admin should be able to see. So
"logging in" with svn list works but logging in to commit doesn't, that's
what i meant.
> 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 :)
Hehe, I can live with that, but I thought this is unwanted behaviour.
According to your answer list should, in my case, only work when --username
is specified, right? Or is there a flaw in my apache config i am not able
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Dec 29 14:08:34 2002