On Fri, Nov 20, 2015 at 04:08:53PM +0000, Vincas.Razma_at_bentley.com wrote:
> Workflow:
>
> 1) Execute HTTPS request – gets response and finishes with CURLE_OK.
>
> 2) Turn off WiFi (or loose connection other way)
>
> 3) Execute HTTPS request – completes after set timeout (usually 3 minutes)
> minutes with CURLE_OPERATION_TIMEDOUT. Same happens if request was in progress
> of downloading data.
>
> 4) Execute HTTPS request – completes instantly with
> CURLE_COULDNT_RESOLVE_HOST. This is true for all subsequent requests.

You don't mention any step where WiFi is turned back on. Naturally, it's hard
to resolve a host without a network connection.

> Is this issue known? We are reproducing this for last two years with various
> iOS versions and several CURL updates.
>
>
>
> iOS 9, Libcurl/7.37.0 OpenSSL/1.0.1p, curl_multi/curl_easy APIs

Which DNS resolver?

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-11-20