From 7b52906dd04b0e49c18dd79f49860c67b3c80a54 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 28 Apr 2025 08:30:16 +0200 Subject: [PATCH] HTTPSRR.md: clarify somewhat Closes #17204 --- docs/HTTPSRR.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/HTTPSRR.md b/docs/HTTPSRR.md index b408a9754f..22184a253e 100644 --- a/docs/HTTPSRR.md +++ b/docs/HTTPSRR.md @@ -11,13 +11,13 @@ DNS Resource Record. curl features **experimental** support for HTTPS RR. -- The ALPN list from the retrieved HTTPS record is parsed -- The ECH field is stored (when DoH is used) -- The port number from the HTTPS RR is not used +- The ALPN list from the record is parsed and used +- The ECH field is stored - and used if ECH is enabled in the build +- The port number is not used (Firefox supports it, Chrome does not) - The target name is not used -- The IP addresses from the HTTPS RR are not used +- The IP addresses (`Ipv6hints`, `Ipv4hints`) from the HTTPS RR are not used - It only supports a single HTTPS RR per hostname -- consider cases without A/AAAA records but *with* HTTPS RR +- Hostnames without A/AAAA records but *with* HTTPS RR fails - consider service profiles where the RR provides different addresses for TCP vs QUIC etc -- 2.47.3