HG Push Locks Account

[Augie Fackler]

Make sure your server responds reasonably - 403 forbidden should be
returned when the user presented wrong credentials, whereas 401
unauthorized should be returned when there were no credentials provided but
some were required.

(I'm pretty sure I got that right - hopefully Mads or someone can correct
me if I got it backwards, which is possible.)


On Wed, Jan 22, 2014 at 1:16 PM, John Trump <trumpjk at gmail.com> wrote:

> If a users enters an incorrect password when trying to push to a
> repository their account gets locked. It appears that hg tries the push
> multiple times using the incorrect password. Is there a way to prevent hg
> from trying multiple times?
>
> $ hg --debug clone http://server:8081/scm/hg/testbeds/dputb<http://sd-ptss-dev1:8081/scm/hg/testbeds/dputb>dputb2
>
> using http://server:8081/scm/hg/testbeds/dputb<http://sd-ptss-dev1:8081/scm/hg/testbeds/dputb>
>
> sending capabilities command
>
> http authorization required
>
> realm: SONIA :: SCM Manager
>
> user: test
>
> password:
>
> http auth: user test, password *
>
> http auth: user test, password *
>
> http auth: user test, password *
>
> http auth: user test, password *
>
> http auth: user test, password *
>
> http auth: user test, password *
>
> abort: authorization failed
>
> Using: Mercurial Distributed SCM (version 2.2.2)
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140122/fc3563cd/attachment.html>