auth errors with nginx + fcgiwrap

[Robin Becker]

On 13/01/2015 19:04, Matt Mackall wrote:
> On Tue, 2015-01-13 at 12:46 +0000, Robin Becker wrote:
>> results in this access.log
>>> hg.host.com 192.168.0.3 - - [13/Jan/2015:12:36:03 +0000] "GET /hg-xxxx/sandbox?cmd=batch HTTP/1.1" 401 188 "-" "mercurial/proto-1.0" 443
>>> hg.host.com 192.168.0.3 - bilbo [13/Jan/2015:12:36:03 +0000] "GET /hg-xxxx/sandbox?cmd=batch HTTP/1.1" 200 211 "-" "mercurial/proto-1.0" 443
>>
>> and this error.log
>>> 2015/01/13 12:36:03 [error] 14939#0: *414 no user/password was provided for basic authentication, client: 192.168.0.3, server: hg.host.com, request: "GET /hg-xxxx/sandbox?cmd=capabilities HTTP/1.1", host: "hg.host.com"
>>> 2015/01/13 12:36:03 [error] 14939#0: *415 no user/password was provided for basic authentication, client: 192.168.0.3, server: hg.host.com, request: "GET /hg-xxxx/sandbox?cmd=batch HTTP/1.1", host: "hg.host.com"
>>
>> I do have a password stored for the bilbo user, but it seems we always try first
>> without auth being set or something. Our jenkins test machine causes the nginx
>> error log to fill up quite rapidly.
>>
>> Is there a way to remedy this problem?
>
> It's totally normal for clients to try first without auth.
>
I realize that, but I don't seem able to get mercurial to include the basic auth 
immediately even if I try making the repo path include a username:password so 
I'll get lots of these errors.

I suppose apache treats lack of auth differently to nginx since I never saw 
these errors with simple cgi. I'll try asking on an nginx list to see if there 
something remedial I can do.
-- 
Robin Becker