On Tue, 3 Mar 2009, Axel Kuhn epidox wrote:

> 0000: CONNECT +++++.+++++.de:443 HTTP/1.0
> 0031: Host: +++++.+++++.de:443
> 0057: Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAA
> 0097: AAAAA=
> 009f: User-Agent: curl/7.19.2 (i386-pc-win32) libcurl/7.19.2 OpenSSL/0
> 00df: .9.8g zlib/1.2.3
> 00f1: Proxy-Connection: Keep-Alive
> 010f: Content-Type: application/x-CIDX
> 0131:
> <= Recv header, 37 bytes (0x25)
> 0000: HTTP/1.1 200 Connection established

This is funny. You specify NTLM but the proxy clearly just let you through
without it.

> Unfortunately no data is sent to the remote server. I assume this is due to
> line "00c4: Content-Length: 0".
>
> So my question is: Why is content-length equal to 0?
> - Is this a bug within curl?
> - Is this a problem with the proxy?

I think it is a bug. libcurl will use content-length 0 for the NTLM auth phase
and judging from your protocol dump here I think it wrongly uses that even
though it got no 407 response. I'll need to setup a little test case a see...

A work-around for you is to simply not specify --proxy-ntlm since the proxy
obviously doesn't care!

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html