This was possibly related to server being buggy (I'm not sure of the
details). Re-writing the server with a different rest framework fixed the
issue. Also don't know how libcurl managed to manifest the issue but curl
command line didn't.

On Sat, Oct 10, 2015 at 5:40 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Fri, 9 Oct 2015, Sanchay Harneja wrote:
>
> I'm following libcurl's getinmemory
>>
>
> ...
>
> realsize=16384
>> * transfer closed with 41842792 bytes remaining to read
>>
>
> ...
>
> But the inbuilt curl binary handles this fine:
>> $ curl 127.0.0.1:8000/abcd/1/ | wc
>>
>
> Wow, that is weird. Can you use strace or wireshark or something to figure
> out exactly what made libcurl consider that connection to be closed? There
> really is no important difference that I can think of between curl and
> libcurl's fetches in these cases.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: 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 2015-10-15