cURL / Mailing Lists / curl-users / Single Mail


Re: how to use --proxy-negotiate, exactly?

From: Dan Fandrich <>
Date: Sun, 22 Feb 2009 21:01:36 -0700

On Mon, Feb 23, 2009 at 02:38:19AM +0000, Brian J. Murrell wrote:
> Yeah. I had to look at the code to actually discover that I needed to
> give it a username. I would have thought it might get that out of the
> credential cache.

Specifying a user acts like a trigger to begin authentication. Windows' SSPI
auth will use the current credentials, but authentication needs to be enabled
by providing a blank user name/password in the form ":". It sounds like if
Negotiate doesn't already do that, it's a feature that could be added. But
that can wait until this problem is solved.

I don't see anything in the trace that looks suspicious, but I'm not an
expert on Negotiate. curl ought to send an authentication header in the
second round, which it doesn't. You could try the latest curl on the
off chance that something was fixed in this area already.

>>> Dan

--              The web change of address service
          Let webmasters know that your web site has moved
List admin:
Received on 2009-02-23