# Caddy v2.10.0 - Product: Caddy (https://whatsnew.fyi/product/caddy) - Vendor: Caddy - Date: 2025-04-18 - Version: v2.10.0 - Original notes: https://github.com/caddyserver/caddy/releases/tag/v2.10.0 - Permalink: https://whatsnew.fyi/product/caddy/releases/v2.10.0 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: release facts (products, versions, dates, links, CVE ids and flags) are open data under CC BY 4.0, from the API at https://whatsnew.fyi/api/v1 or the nightly dataset at https://github.com/whatsnew-fyi/dataset. The summaries, labels and curation are © What's New: quote freely with attribution and a link back; wholesale republication of them is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- Changes to check: - **Behavior changed:** `Via header` (inferred by a model) - **Behavior changed:** `wildcards` (inferred by a model) - **Removed:** `auto_https prefer_wildcard` (inferred by a model) - **Requirement raised:** `Go` → `latest minor Go version` (inferred by a model) - **Requirement raised:** `libdns` → `1.0` (inferred by a model) - **added** — Support for Encrypted ClientHello (ECH) to encrypt the ClientHello portion of TLS connections including the domain name - **added** — Support for post-quantum key exchange using the standardized x25519mlkem768 cryptographic group - **added** — ACME profiles as an experimental draft to choose certificate properties with more flexibility than traditional CSR methods - **added** — Global DNS provider configuration option to specify a default DNS module instead of configuring it locally in every part of the config - **changed** — Reverse proxy now sets a Via header instead of a duplicate Server header - **changed** — Wildcards are now utilized by default for subdomains instead of obtaining individual certificates - **changed** — Support for libdns 1.0 APIs with updated interfaces for DNS provider modules - **changed** — Only the latest minor Go version is now supported instead of the last 2 minor versions - **removed** — Remove experimental auto_https prefer_wildcard option Caddy 2.10 is here! Aside from bug fixes, this release features: - **Encrypted ClientHello (ECH):** This new technology encrypts the last plaintext portion of a TLS connection: the ClientHello, which includes the domain name being connected to. The [draft spec](https://www.ietf.org/archive/id/draft-ietf-tls-esni-24.html) for ECH is almost finalized, so we can now support this privacy feature for TLS. This is a powerful but nuanced capability; we highly recommend reading [the ECH documentation](https://caddyserver.com/docs/automatic-https#encrypted-clienthello-ech) on our website. - **Post-quantum (PQC) key exchange:** Caddy now supports the standardized `x25519mlkem768` cryptographic group by default. - **ACME profiles:** ACME profiles are an experimental draft that allow you to choose properties of your certificates with more flexibility than traditional CSR methods. For example, [Let's Encrypt will issue 6-day certificates](https://letsencrypt.org/2025/01/16/6-day-and-ip-certs/) under a certain profile. Caddy may eventually use that profile by default. - **Via header:** The reverse proxy now sets a Via header instead of a duplicate Server header. - **Global DNS provider:** You can now specify a default "global" DNS module to use instead of having to configure it locally in every part of your config that requires a DNS provider (for example, ACME DNS challenges, and ECH). This is the `dns` global option in the Caddyfile, or in JSON config, it's the `dns` parameter in the `tls` app configuration. - **Wildcards used by default:** Previously, Caddy would obtain individual certificates for every domain in your config literally; now wildcards, if present, will be utilized for subdomains, rather than obtaining individual certificates. This change was motivated by the novel possibility for subdomain privacy afforded by ECH. It can be overridden with `tls force_automate` in the Caddyfile. The experimental `auto_https prefer_wildcard` option has been removed. - **libdns 1.0 APIs:** Many of you use [DNS provider modules](https://github.com/caddy-dns) to solve ACME DNS challenges or to enable dynamic DNS. They implement interfaces defined by [libdns](https://github.com/libdns/libdns) to get, set, append, and delete DNS records. After 5 years of production experience, including lessons learned with ECH, libdns APIs have been updated and 1.0 beta has been tagged. DNS provider packages will need to update their code to be compatible, which will help ensure stability and well-defined semantics for the future. Several packages have already updated or are in the process of updating (cloudflare, rfc2136, and desec to name a few). - **Global `dns` config:** Now that several components of Caddy configuration may affect DNS records (ACME challenges, ECH publication, etc.), there is a new `dns` global option that can be used to specify your DNS provider config in a single place. This prevents repetition of credentials for servers where all the domains are managed by a single DNS provider. **Thank you to the many contributors who have helped to make this possible!** :tada: :partying_face: :champagne: :warning: While have traditionally supported the last 2 minor Go versions to accommodate some distribution / package manager policies, we now only support the latest minor Go version. The privacy and security benefits added in new Go versions (such as post-quantum cryptography) are worth making available to everyone as soon as possible, rather than holding back the entire user base or maintaining multiple code compilation configurations. ##### Encrypted ClientHello (ECH) details (This is a brief overview. We recommend reading [the full documentation](https://caddyserver.com/docs/automatic-https#encrypted-clienthello-ech).) Typically, server names (domain names, or "SNI") are sent in the plaintext ClientHello when establishing TLS connections. With ECH, the true server name is encrypted (and wrapped) by an "outer" ClientHello w _[Truncated at 4000 characters — full notes: https://github.com/caddyserver/caddy/releases/tag/v2.10.0]_