Hello Daniel,

>> now. on some people, retcode is 100, res is 0. but no data received. it's
>> supposed to receive an "OK" or some error code with a little descriptive
>> text. so, return value from the http server is between 2 and 32 chars.
DS> Can you figure out all the response headers you receive when this happens? In
DS> my view, it looks like the server only sends back that single 100 response.
DS> That would cause this end result.

What's supposed to happen in a normal situation? I mean a normal
situation with a 100-continue response. 100-continue, more data from
client, then 200-OK?

the server should be fine because it works with other clients, same
code, different data posted.

to be blunt, any way to turn off that 100-continue response off the
server? maybe i force the server to use 1.0 with something like this:
BrowserMatch "bla bla" nokeepalive downgrade-1.0 force-response-1.0

what do you think?

DS> Have you tried libcurl 7.11.0 to see if that cures the problem?

ok, i will.

-- 
Kemal