Date: Tue, 20 Jan 2009 12:55:21 +0100 (CET)
On Tue, 20 Jan 2009, Bharat Varma wrote:
> Here are my observations so far after some tests I ran yesterday.. I don't
> know much about whether the curl headers dump gives any info about whether
> the proxy is NTLM or NTLM v2. But information below might help.
The easiest way is to define the DEBUG_ME define in lib/http_ntlm.c and read
the verbose output from that.
> 1. Tried program based on curl 7.17.x some 10 months back ( may be an
> earlier version.. Whatever was the version that was latest last year this
> time) in an NTLM environment. I remember thinking it is NTLMv2. I failed to
> connect through the proxy.
Right, libcurl doesn't support NTLMv2 so there's no surprise there.
> 2. Tried SSPI & SSL enabled Curl 7.19.2 this time - same environment.
> On this socket, I ran a trivial echo protocol and I got through without any
> hassles. I am going to run a couple more with a binary data transfer
> protocol this time and will update this list based on the observations. If
> there is any way I can dump headers so that we can see if it is NTLM or
> NTLMv2, I can write a small program and post the headers.
Sure, VERBOSE and DEBUGFUNCTION will show headers and the code in
lib/http_ntlm.c should be able to offer some hints on how to interpret things
- at least as long as they are NTLMv1 or generic NTLM (if there is any such
-- / daniel.haxx.seReceived on 2009-01-20