Daniel Stenberg wrote:

> On Fri, 24 Jun 2005, Andrew Bushnell wrote:
>
>> It has to do with the fact that as part of my own headers I was
>> specifying as part of my post, one of the headers was
>> 'Content-length'. Even though this length was correctly set, its
>> specification was somehow intefering with the NTLM negotiating that
>> was going on. By not specifying this header and letting libcurl build
>> it itself, things worked fine. I have updated my code and have gotten
>> further along.
>
>
> The Content-Length - and other headers - involved when doing multi-pass
> authentications (and especially NTLM) with POST have been carefully
> crafted back and forth over the years, and setting your own in this case
> is a good way to break libcurl's ability to do right!
>
> Anyway, it is good to hear you got it working!
>
Out of curiosity, what other headers are problematic. The we also have
to issue the content-type as we post xml data for the soap transactions,
  does not as of yet, seem to be causing problems, but was double checking.

-- 
************************************
Andrew Bushnell
Lead Development Engineer
Fluent Inc.
10 Cavendish Court
Centerra Resource Park
Lebanon, NH  03766
awb_at_fluent.com
Phone: 603-643-2600, ext. 757
Fax: 603-643-1721
www.fluent.com
************************************
_______________________________________________
http://cool.haxx.se/mailman/listinfo/curl-and-python