Lines Matching +full:- +full:- +full:enable +full:- +full:ares

1 <!--
4 SPDX-License-Identifier: curl
5 -->
9 [RFC 9460](https://www.rfc-editor.org/rfc/rfc9460.html) documents the HTTPS
14 - The ALPN list from the retrieved HTTPS record is parsed
15 - The ECH field is stored (when DoH is used)
16 - The port number from the HTTPS RR is not used
17 - The target name is not used
18 - The IP addresses from the HTTPS RR are not used
19 - It only supports a single HTTPS RR per hostname
20 - consider cases without A/AAAA records but *with* HTTPS RR
21 - consider service profiles where the RR provides different addresses for TCP
24 `HTTPSRR` is listed as a feature in the `curl -V` output if curl contains
25 HTTPS RR support. If c-ares is not included in the build, the HTTPS RR support
28 `asyn-rr` is listed as a feature in the `curl -V` output if c-ares is used for
32 The data extracted from the HTTPS RR is stored in the in-memory DNS cache to
44     ./configure --enable-httpsrr
48     cmake -DUSE_HTTPSRR=ON
64 ## Non-DoH
67 provide the ability using the regular resolver backends. We use the c-ares DNS
70 ### c-ares
72 If curl is built to use the c-ares library for name resolves, an HTTPS RR
79 build still needs a c-ares installation provided so that a separate request
83 This is done by specifying both c-ares and threaded resolver to configure:
85     ./configure --enable-ares=... --enable-threaded-resolver
89     cmake -DENABLE_ARES=ON -DENABLE_THREADED_RESOLVER=ON
95 c-ares), the `curl -V` output looks exactly like a c-ares resolver build.