From: Daniel Stenberg <daniel@haxx.se>
Date: Mon, 28 Apr 2025 06:30:16 +0000 (+0200)
Subject: HTTPSRR.md: clarify somewhat
X-Git-Tag: curl-8_14_0~194
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7b52906dd04b0e49c18dd79f49860c67b3c80a54;p=thirdparty%2Fcurl.git

HTTPSRR.md: clarify somewhat

Closes #17204
---

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