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

requesting all changes

     2

adding changesets

     3

adding manifests

     4

adding file changes

     5

added 1 changesets with 4 changes to 4 files

     6

updating to branch default

     7

4 files updated, 0 files merged, 0 files removed, 0 files unresolved

     8

requesting all changes

     9

adding changesets

    10

adding manifests

    11

adding file changes

    12

added 1 changesets with 4 changes to 4 files

    13

updating to branch default

    14

4 files updated, 0 files merged, 0 files removed, 0 files unresolved