Mercurial > hg
comparison doc/hgrc.5.txt @ 8333:89c80c3dc584
allow http authentication information to be specified in the configuration
author | Sune Foldager <cryo@cyanite.org> |
---|---|
date | Mon, 04 May 2009 20:26:27 +0200 |
parents | 9a1b86cfd29e |
children | 493d23d923ea |
comparison
equal
deleted
inserted
replaced
8332:3e544c074459 | 8333:89c80c3dc584 |
---|---|
97 -------- | 97 -------- |
98 | 98 |
99 This section describes the different sections that may appear in a | 99 This section describes the different sections that may appear in a |
100 Mercurial "hgrc" file, the purpose of each section, its possible | 100 Mercurial "hgrc" file, the purpose of each section, its possible |
101 keys, and their possible values. | 101 keys, and their possible values. |
102 | |
103 [[auth]] | |
104 auth: | |
105 Authentication credentials for HTTP authentication. | |
106 Each line has the following format: | |
107 | |
108 <name>.<argument> = <value> | |
109 | |
110 where <name> is used to group arguments into authentication entries. | |
111 Example: | |
112 | |
113 foo.prefix = hg.intevation.org/mercurial | |
114 foo.username = foo | |
115 foo.password = bar | |
116 foo.schemes = http https | |
117 | |
118 Supported arguments: | |
119 | |
120 prefix;; | |
121 Either '*' or a URI prefix with or without the scheme part. The | |
122 authentication entry with the longest matching prefix is used | |
123 (where '*' matches everything and counts as a match of length 1). | |
124 If the prefix doesn't include a scheme, the match is performed against | |
125 the URI with its scheme stripped as well, and the schemes argument, | |
126 q.v., is then subsequently consulted. | |
127 username;; | |
128 Username to authenticate with. | |
129 password;; | |
130 Optional. Password to authenticate with. If not given the user will be | |
131 prompted for it. | |
132 schemes;; | |
133 Optional. Space separated list of URI schemes to use this authentication | |
134 entry with. Only used if the prefix doesn't include a scheme. Supported | |
135 schemes are http and https. They will match static-http and static-https | |
136 respectively, as well. | |
137 Default: https. | |
138 | |
139 If no suitable authentication entry is found, the user is prompted for | |
140 credentials as usual if required by the remote. | |
102 | 141 |
103 [[decode]] | 142 [[decode]] |
104 decode/encode:: | 143 decode/encode:: |
105 Filters for transforming files on checkout/checkin. This would | 144 Filters for transforming files on checkout/checkin. This would |
106 typically be used for newline processing or other | 145 typically be used for newline processing or other |