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

Re: Re: Aw: No author problem for svn server

From: <wangji_at_htche.com>
Date: Sat, 21 Mar 2015 18:57:19 +0800

That's what I'm doing right now. thank you Andreas
Jeff

 From: Andreas StiegerDate: 2015-03-21 16:04To: usersCC: wangji_at_htche.comSubject: Re: Aw: No author problem for svn serverHi,
 
On 20/03/15 16:54, Andreas Stieger wrote:
> Your configuration requires a password for reading, but everyone (!) can commit.
> This should be the other way around, e.g.
> <LimitExcept GET PROPFIND OPTIONS REPORT>
>
> See https://subversion.apache.org/faq.html#no-author why you have no author without auth challenge.
 
I would like to pre-empt Jeff's question brought to me privately:
To require authentication for ALL operations, which one can assume is
desired for a corporate deployment, simply do not wrap in  <Limit> and
<LimitExcept> at all, this making the "Require valid-user" requirement
effective for all requests. You may refer to the Apache httpd
documentation for detail on this.
 
Andreas
Received on 2015-03-21 11:58:48 CET

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