From 1a5466c9c8ac66a2ebd4a4b89692db504bb64a31 Mon Sep 17 00:00:00 2001 From: Francis Lavoie Date: Wed, 22 Nov 2023 06:31:18 -0500 Subject: [PATCH] Adjust on-demand demo --- new/index.html | 9 +++++++++ new/on-demand-tls.html | 18 +++++++++--------- 2 files changed, 18 insertions(+), 9 deletions(-) diff --git a/new/index.html b/new/index.html index c26b652..800c131 100644 --- a/new/index.html +++ b/new/index.html @@ -227,6 +227,15 @@

Point any subdomain named caddydemo to:

+

A diff --git a/new/on-demand-tls.html b/new/on-demand-tls.html index ce24099..cdb39f1 100644 --- a/new/on-demand-tls.html +++ b/new/on-demand-tls.html @@ -32,7 +32,7 @@ What happened?

- Caddy automatically obtained a certificate for your domain, {{.Req.Host}}, without any change to the server's configuration. We call this technology On-Demand TLS, and it's an exclusive feature of Caddy. + Caddy automatically obtained a certificate for your domain, {{.Req.Host}}, without any change to the server's configuration. We call this technology On-Demand TLS, and it's an exclusive feature of Caddy.

With On-Demand TLS, no config changes are required to serve more domains over HTTPS. This is perfect for servers hosting content or APIs for customer-owned domains because your HTTPS deployment scales as tall and wide as your business does. @@ -60,7 +60,7 @@

1. Prevent abuse

- First, you'll configure an internal endpoint that Caddy can "ask" if a certificate should be allowed for a domain. This endpoint usually looks up the domain in a list or database and returns HTTP 200 if it's allowed. + First, you'll configure an internal endpoint that Caddy can "ask" if a certificate should be allowed for a domain. This endpoint usually looks up the domain in a list or database and returns HTTP 200 if it's allowed. Make sure to reject domains you don't recognize. This means that customers must register their domain with your app first.

@@ -99,7 +99,7 @@

1. Point DNS records

- The owner of the domain sets A and/or AAAA records to point to your Caddy instance. + The customer sets a CNAME record on a domain or subdomain they control, so that their domain resolves to your domain's IP address.