hgweb: do not ignore [auth] if url has a username (issue2822) The [auth] section was ignored when handling URLs like: http://user@example.com/foo Instead, we look in [auth] for an entry matching the URL and supplied user name. Entries without username can match URL with a username. Prefix length ties are resolved in favor of entries matching the username. With: foo.prefix = http://example.org foo.username = user foo.password = password bar.prefix = http://example.org/bar and the input URL: http://user@example.org/bar the 'bar' entry will be selected because of prefix length, therefore prompting for a password. This behaviour ensure that entries selection is consistent when looking for credentials or for certificates, and that certificates can be picked even if their entries do no define usernames while the URL does. Additionally, entries without a username matched against a username are returned as if they did have requested username set to avoid prompting again for a username if the password is not set. v2: reparse the URL in readauthforuri() to handle HTTP and HTTPS similarly. v3: allow unset usernames to match URL usernames to pick certificates. Resolve prefix length ties in favor of entries with usernames.

     1

  $ hg init a

     2

  $ echo a > a/a

     3

  $ hg -R a ci -A -m a

     4

  adding a

     5

     6

  $ hg clone a b

     7

  updating to branch default

     8

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

     9

    10

  $ echo b > b/b

    11

  $ hg -R b ci -A -m b

    12

  adding b

    13

    14

  $ chmod 100 a/.hg/store

    15

    16

  $ hg -R b push a

    17

  pushing to a

    18

  abort: could not lock repository a: Permission denied

    19

  [255]

    20

    21

  $ chmod 700 a/.hg/store

    22