Chris Brown wrote:
> I have spent the last couple of days continuing to investigate this
> problem. I successfully used CURLOPT_DEBUGFUNCTION from the example you
> gave and can see the client receiving the 'Continue 100' from the server.
> It also shows the '=> Send data' output but as far as I can tell the
> request never actually leaves the client. Unfortunately I am unable to
> install Wireshark or anything similar on the client to confirm this but
> unlike the previous requests the request never actually reaches the server
> and timesout. From what I can tell from debugging the Curl_http() function
> (amongst others) it appears to behaving correctly. Is there a lower level
> function I can add some further debugging to check if the request is being
> sent at the latest point in the process?

If your client is on Linux, you can use the "strace" program to trace
the system calls which will show if libcurl _really_ sends the POSTed
data. Use "strace -s 1000" or so to see plenty of data.

On other OSes, there is often a similar system call tracing program.
E.g. on Solaris I think it's called truss, on Cygwin there's
something, and on Windows there are various debuggers which can do it.

-- Jamie
Received on 2008-09-02