On Wed, 5 Jul 2006, mihir gore wrote:

> However on some machines.
> a. http post is sent to server with xml data
> b. server acknowledges
> c. server sends a 100 response
> d. server sends a 200 response.
> whats happening here is that the http status 100 sent causes curl to close
> the socket, so the http 200 is not caught.

Why does the 100 cause curl to close the socket? And when it does this, does
the server reveal anything useful in its logs?

> Alll machines have the same OS (windows xp), the server is IIS 5.0, ( I am
> testing against moveable-type blog server).
>
> I am new to curl, please let me know if you need more info.

Tell us what libcurl version you use.

And then please show us as much as you can: what headers did libcurl send,
what headers did it receive etc. Basically a DEBUGFUNCTION trace. Possibly you
can debug this with the command line tool and use the --trace-ascii option.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html