Hi,

Looking at the packets, receiver sends out a TCP ZeroWindow (followed by
some window update). Server sends out the next packet with FIN (causing the
close connection). So seems like the issue is with the rate at which data
is transferred by the server and the rate at which it's consumed by the
client and the TCP receive buffer size. Apart from changing the TCP window
size, does libcurl provides anything to manage this sort of stuff ? Or if
there is any other potential solutions that could be used to resolve this
issue.

Thanks
Sunny

On Tue, Oct 15, 2013 at 12:06 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Mon, 14 Oct 2013, Sunny Khatri wrote:
>
> Please don't top-post, it makes following this thread totally confusing
> and hard to figure out to what you're referring to here...
>
>
> After some more debugging, I see "Closing connection #0". I think it
>> might be related to this error. Does it has to do anything with the
>> keep-alive timeout or something else ?
>>
>
> That's just the message libcurl outputs when it decided to close its end
> of the connection, which very well could be the result of the fact that the
> server already closed it from its end...
>
>
> --
>
> / daniel.haxx.se
> ------------------------------**------------------------------**-------
> List admin: http://cool.haxx.se/list/**listinfo/curl-library<http://cool.haxx.se/list/listinfo/curl-library>
> Etiquette: http://curl.haxx.se/mail/**etiquette.html<http://curl.haxx.se/mail/etiquette.html>
>

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