{"author":"Daniel Stenberg","author_email":"daniel@haxx.se","author_time":1737456140,"commit_time":1737845174,"committer":"Daniel Stenberg","committer_email":"daniel@haxx.se","hash":"0d4fdbf15d8eec908b3e63b606f112b18a63015e","message":"asyn-thread: use c-ares to resolve HTTPS RR\n\nAllow building with c-ares and yet use threaded resolver for the main\nhost A/AAAA resolving:\n\n  `--with-ares` provides the c-ares install path and defaults to use\n  c-ares for name resolving\n\n  `--with-threaded-resolver` still uses c-ares in the build (for HTTPS)\n  but uses the threaded resolver for \"normal\" resolves.\n\nIt works similarly for cmake: ENABLE_ARES enables ares, and if\nENABLE_THREADED_RESOLVER also is set, c-ares is used for HTTPS RR and\nthe threaded resolver for \"normal\" resolves.\n\nHTTPSRR and c-ares-rr are new features return by curl_version_info() and\nthus shown by curl -V.\n\nThe c-ares-rr feature bit is there to make it possible to distinguish\nbetween builds using c-ares for all name resolves and builds that use\nthe threaded resolves for the regular name resolves and c-ares for\nHTTPSRR only. \"c-ares-rr\" means it does not use c-ares for \"plain\" name\nresolves.\n\nHTTPSRR support is EXPERIMENTAL only.\n\nCloses #16054\n","parents":["520e67dd39f964648bfa68ed2401f270193b14cc"],"tree_hash":"b0bc11828fab116a29032e434c3863e4d4c781dd"}