The Caddy reverse-proxy tutorial's `on_demand_tls` example told readers to leave `ask http://example.com` unchanged, warning that changing it could break cert issuance. That's backwards: Caddy calls the `ask` URL with the requested hostname as a `domain` query parameter and treats any `2xx` response as approval to issue a certificate. `example.com` returns `200` for any request, so the documented config approved certificate issuance for any hostname, letting an attacker exhaust the deployment's Let's Encrypt rate limit for the whole domain. Replaces the "DO NOT CHANGE" warning with guidance to point `ask` at a real, self-hosted validation endpoint, and links to [the discussion](https://github.com/coder/coder/discussions/29079#discussioncomment-18462842) that reported this for a reference implementation. Reported in https://github.com/coder/coder/discussions/29079 > This PR was created with AI assistance (Coder Agents).