Dan,

Thanks for your response. The whole operation took only 6 minutes and got
timed out. Also I can confirm the response bytes by redirecting it to a
file. It has around 200 Kilo Bytes of size. So in an interval of 6 minutes,
client got response from the server but still it gets timed out. As I have
redirected the response bytes to a file, I don't need network sniffer in my
case. I believe the below curl prints mean bytes received by the client and
not the bytes sent from the client,

*> * Operation timed out after 360000 milliseconds with 205512 bytes
received *
*> * Closing connection #0 *
*> * Timeout was reached

Please correct me if I am wrong.

*Is there anything wrong with this curl print ( I posted it in my first
thread),

* SSL re-using session ID* SSL connection using AES256-SHA* old SSL
session ID is stale, removing

Does it mean any problem here ? Meanwhile I will try upgrading my libcurl
to the latest version and let you know.

Thanks,
Venkat

From: Dan Fandrich
<dan_at_coneharvesters.com<dan_at_coneharvesters.com?Subject=Re:%20LibCurl%20Time%20out%20Issue>>

Date: Fri, 25 Jan 2013 21:14:36 +0100

On Fri, Jan 25, 2013 at 05:39:16PM +0530, Venkatesh Prabu Narayanan wrote:
*> I am new to this forum. I am using libcurl to download files from the
server to *
*> the client. I am using the following options in my curl connection in
client *
*> side, *
*> *
*> curl_easy_setopt(curlPtr, CURLOPT_LOW_SPEED_LIMIT, 1); *
*> curl_easy_setopt(curlPtr, CURLOPT_LOW_SPEED_TIME, 360L); *
*> curl_easy_setopt(curlPtr, CURLOPT_IGNORE_CONTENT_LENGTH, 1); *
*> curl_easy_setopt(curlPtr, CURLOPT_TCP_NODELAY, 1); *
*> *
*> Even though I have made it to time out only if no bytes was received for
a *
*> period of 6 minutes (360 seconds), the operation seems to be timed out
even *
*> after receiving response bytes within the stipulated time. *
[...]
*> * Operation timed out after 360000 milliseconds with 205512 bytes
received *
*> * Closing connection #0 *
*> * Timeout was reached *

This is what would be expected if the client sent 205512 bytes and then the
server stopped responding for 360 seconds. You didn't say how long it was
from the start of the transfer before this timeout was reached, or how you
know
that the response bytes were actually being received. A network sniffer
would tell you where the problem lies.

*>>> Dan *

*> I am using the libcurl version 7.19.3. I know it is an older version.
But *
*> please let me know what is went wrong here. Does upgrading to latest
version *
*> help in my case. I would appreciate your answer. *

Why don't you try it and see?
*>>> Dan *

On Fri, Jan 25, 2013 at 5:39 PM, Venkatesh Prabu Narayanan <
venkateshprabu06_at_gmail.com> wrote:

> Hi there,
>
> I am new to this forum. I am using libcurl to download files from the
> server to the client. I am using the following options in my curl
> connection in client side,
>
> curl_easy_setopt(curlPtr, CURLOPT_LOW_SPEED_LIMIT, 1);
> curl_easy_setopt(curlPtr, CURLOPT_LOW_SPEED_TIME, 360L);
> curl_easy_setopt(curlPtr, CURLOPT_IGNORE_CONTENT_LENGTH, 1);
> curl_easy_setopt(curlPtr, CURLOPT_TCP_NODELAY, 1);
>
> Even though I have made it to time out only if no bytes was received for a
> period of 6 minutes (360 seconds), the operation seems to be timed out even
> after receiving response bytes within the stipulated time.
>
> Here is my response in client side. I have edited ssl certificate details
> for confidentiality.
>
> * Connection #0 seems to be dead!* Closing connection #0* About to connect() to 10.0.0.137 port 34007 (#0)* Trying 10.0.0.137... * TCP_NODELAY set* connected* Connected to 10.0.0.137 (10.0.0.137) port 34007 (#0)* SSL re-using session ID* SSL connection using AES256-SHA* old SSL session ID is stale, removing* Server certificate:* SSL certificate verify result: self signed certificate (18), continuing anyway.
> > POST /filedownload?&actdatalen=363768 HTTP/1.1
> Host: 10.0.0.137:34007
> Accept: */*
>
> Content-Length: 363909
>
> Expect: 100-continue
>
> Content-Type: multipart/form-data; boundary=----------------------------c0cba712b577
>
> Unable to Send IPC message. Error is 6
> Reconnecting to IPC listener failled.
> * Done waiting for 100-continue
> * HTTP 1.0, assume close after body
> < HTTP/1.0 200 OK
> < Content-Type: text/plain
> <
>
> * Operation timed out after 360000 milliseconds with 205512 bytes received
> * Closing connection #0
> * Timeout was reached
>
> I am using the libcurl version 7.19.3. I know it is an older version. But
> please let me know what is went wrong here. Does upgrading to latest
> version help in my case. I would appreciate your answer.
>
> P.S Kindly redirect the mailing group if I am mailed to wrong mailing list.
>
> Regards,
> Venkat
>

-- 
Thanks and Regards
N.Venkatesh Prabu

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-01-28