Re: "Connection is still name resolving, can't reuse" error

On Tue, 2 Jun 2020, Leo Song wrote:

> 1. The way I am using cURL and share the pool is via AWS S3 SDK.
>
> Do you think this way of sharing connection essentially doing the same as my
> previous approach with connection cache sharing (CURLSH)?

First: if you're using their code you should ask them for help with it.

That's 800 lines of code in that file, I don't know what they do but I can
tell you for sure that they *cannot* offer even something similar to the
connection cache sharing that libcurl does itself because the connection pool
is internal and not externally accessible.

> 2. Yes. I tried disabling the header by setting CURLOPT_EXPECT_100_TIMEOUT_MS
> to 0, and the 100-continue did not occur. I am just not sure if this is
> going to cause any side effect, even though I have not seen any yet.

You disable the header (any HTTP header really) with CURLOPT_HTTPHEADER.

-- 
  / daniel.haxx.se | Commercial curl support up to 24x7 is available!
                   | Private help, bug fixes, support, ports, new features
                   | https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html