Thanks much, Daniel, for helping us interpret the debug messages. I'll try
to dig in a bit at the code site you pointed out.

Ray: I pulled the latest source on GitHub as of Thursday, Feb 23 and built
a debug libcurl to reproduce this failure. I'll take a look at the issue
you pointed out. Thanks!

On Fri, Feb 24, 2017 at 10:03 AM, Ray Satiro via curl-library <
curl-library_at_cool.haxx.se> wrote:

> On 2/23/2017 7:00 AM, Daniel Stenberg wrote:
>
> [466] Operation timed out after 0 milliseconds with 0 out of 0
> bytes received␊
>
>
> This is a really strange message here that possible indicates a problem.
>
> This is likely the timeout check at multi.c:1370. It calls Curl_timeleft()
> to figure out how much time there's left for this transfer and it somehow
> thinks that there is no time left and yet it then says "0 milliseconds"
> have passed.
>
>
> What libcurl version? Could this be related to
> https://github.com/curl/curl/issues/619
>
>
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-02-28