On Mon, 27 Jun 2005, Andrew Bushnell wrote:

>> 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!

> 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.

(Proxy-)Authorization:, Connection: and of course the request keyword itself
are the ones that I can think of off the top of my head.

I guess the thumb rule is to only change/add those headers you really must,
and leave the others to be dealt with by libcurl itself - if in doubt.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
_______________________________________________
http://cool.haxx.se/mailman/listinfo/curl-and-python