On Thu, 23 Feb 2017, Pushkar Kulkarni wrote:

> [466] Re-using existing connection! (#0) with host api.github.com␊

A new transfer is initiated and it found an existing connection it can reuse
in the connection cache.

> [466] Connected to api.github.com (192.30.253.116) port 443 (#0)␊

That's info about said connection.

> [466] STATE: CONNECT => DO handle 0x7f0b3045d348; line 1464
> (connection #0)␊

This is a state change. The connect phase is done and it goes over to the DO
state. In the DO state the action is performed that triggers the upcoming file
transfer. (Often a GET request in the HTTP case.)

> [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.

> [466] multi_done␊

This gets called after a request has completed, even if in this case the
completion is "premature" - it happens before the end of the full data
transfer.

> [466] Closing connection 0␊

When finishing a transfer before the full data, in most cases libcurl needs to
close the connection since it cannot be reused safely anymore at that point.
That's what happens here.

> [466] The cache now contains 1 members␊

This says there's a new connection added to the connection cache.

> [466] => Send SSL data ␕␃␃␀␚

Info about the SSL data that libcurl sends.

-- 
  / daniel.haxx.se

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