On 10/16/05, Ben Collins-Sussman <email@example.com> wrote:
> On 10/16/05, Ivan Zhakov <firstname.lastname@example.org> wrote:
> > Agreed that CHANGES should be summary, but this fix important and I
> > have complained. The subversion says reqiuere enter new password,
> > although problems that you haven't commit access to area, it is
> > annoying. And users might be glad to know that this is fixed.
> I would argue that since you're the first person to notice the bug in
> the two years since mod_authz_svn was written, that *no* users will be
> glad to know that it's fixed.
> My opinion is that when mod_authz_svn disallows access to a path,
> users notice that they "can't access the path", but don't care about
> the exact details of the error. It failed, and that's what matters.
> Previously, the svn client prompted them twice before throwing error.
> And now it will throw a "forbidden" error instead. I don't think
> users have ever noticed the exact error, and don't think they'll
> notice the new, "correct" error message in 1.3. I suspect that the
> only reason you noticed the bug is because you're paying careful
> attention to the HTTP specification. ;-)
I haven't 1.3.x server, but fixed version should have different
behavior than pre 1.3.x: when user accesses forbidden path served on
pre 1.3.x server subversion says: "no access, please enter new
username and password", but new server should (I hope) say only no
access without asking for username/password. If it is otherwise, than
I also don't see reason include this change in CHANGES.
Received on Fri Oct 21 16:46:06 2005
This is an archived mail posted to the Subversion Dev