Hi, 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 ?
Thanks Sunny On Fri, Oct 11, 2013 at 3:20 PM, Sunny Khatri <[email protected]> wrote: > Yup, Wireshark reports incomplete data sent by the server ( and hence > missing 0 at the end). Funny thing here is that I see this error only when > I'm debugging with GDB and continue after some time. > > > > > On Fri, Oct 11, 2013 at 1:45 PM, Daniel Stenberg <[email protected]> wrote: > >> On Fri, 11 Oct 2013, Sunny Khatri wrote: >> >> This issue has been discussed in the past but I'm occasionally getting >>> this error (and I'm not using EXPECT:100 continue header). Any pointers on >>> what could be going on ? Timeouts ? Server Side issue ? >>> >> >> It means that the TCP connection were closed before all data was read. I >> would guess it is due to the server side but you probably need to wireshark >> it to figure out the exact details. >> >> -- >> >> / 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
