On Fri, 25 Jan 2002, Dale Counts wrote:

[ POST command line cut off ]

Thanks for your detailed report. Comments follow inlined below.

> The Server accepts and processes the data(most of the time) but curl
> 'hangs' receiving the output, trying to debug it with -v gives
> ______________
> > POST /exec/Admin? HTTP/1.1
> User-Agent: curl/7.9.3 (i686-pc-linux-gnu) libcurl 7.9.3 (OpenSSL
> 0.9.6c)
> Host: secureURL
> Pragma: no-cache
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
> Cookie: session=lotsof Secret Cookies
> Content-Length: 1922
> Expect: 100-continue
> Content-Type: multipart/form-data;
> boundary=curl8WLsiblEgUsh232g5RHeugVYymk

[snip]

> curl: (28) Operation timed out with 5979 out of -1 bytes received

Can you also show us the headers the server replied? With -i or "-D -".

> the timeout -m 60 was set because it will hang forever(or a long time)
> without it in this example the 5979 bytes it received is how many it is
> supposed to 'curl: (28) Operation timed out with 5979 out of -1 bytes
> received' is it really looking for -1 bytes or is that just part of the
> timeout command is it possible the server is holding the connection open??

-1 is just an internal for "unknown size" which seems to indicate that there
was no Content-Length: in the reply headers.

Without a known size, the server must close the connection to signal to the
client when the transfer is done and this looks as if curl perhaps doesn't
really notice the closure.

> any ideas

7.9.3 has brand new non-blocking sockets internally, which might have
introduced a few problems like this. If you need this working really fast,
I'd suggest you downgrade and try 7.9.2.

Of course, we still need to fix 7.9.3 if this truly is a bug.

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/