Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
HTTPS-RR and ECH
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 30 Jul 2026 09:30:35 +0200 (CEST)
Hello friends,
I would like us to make an effort to move curl's HTTPS-RR and ECH support out
of experimental mode before end of year 2026.
We need HTTPS-RR to do proper ECH, and as a side-effect we can do HTTP/3
better once more servers start to announce their support there. HTTPS-RR is a
super complicated record and I believe not even the browsers support every
possible thing this provides. curl's support is still only partial but I
believe it could still be worth shipping, and then expand support over time
once we see servers deploy and use more parts of it.
We want ECH enabled to push online privacy forward.
For HTTPS-RR support, curl needs to be built with c-ares even if still told to
do "normal" name resolves using the threaded name resolver. There is also no
options or ways to control or disable attempted HTTPS-RR use in runtime once
enabled in the build. Do we need that?
For ECH support, curl needs to be built with an OpenSSL fork or wolfSSL for
TLS.
Thoughts?
Date: Thu, 30 Jul 2026 09:30:35 +0200 (CEST)
Hello friends,
I would like us to make an effort to move curl's HTTPS-RR and ECH support out
of experimental mode before end of year 2026.
We need HTTPS-RR to do proper ECH, and as a side-effect we can do HTTP/3
better once more servers start to announce their support there. HTTPS-RR is a
super complicated record and I believe not even the browsers support every
possible thing this provides. curl's support is still only partial but I
believe it could still be worth shipping, and then expand support over time
once we see servers deploy and use more parts of it.
We want ECH enabled to push online privacy forward.
For HTTPS-RR support, curl needs to be built with c-ares even if still told to
do "normal" name resolves using the threaded name resolver. There is also no
options or ways to control or disable attempted HTTPS-RR use in runtime once
enabled in the build. Do we need that?
For ECH support, curl needs to be built with an OpenSSL fork or wolfSSL for
TLS.
Thoughts?
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2026-07-30