mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-06-22 14:10:32 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

review

Browse source
This commit is contained in:
Francis Lavoie 2022-03-11 15:05:11 -05:00
parent 8adcfcbffc
commit 60f69d56d5
No known key found for this signature in database
GPG key ID: 29B92EA7430C3C62
2 changed files with 34 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

66
src/docs/markdown/api.md
View file

@ -96,33 +96,33 @@ Export entire config and pretty-print it:
<pre><code class="cmd"><span class="bash">curl "http://localhost:2019/config/" | jq</span> <pre><code class="cmd"><span class="bash">curl "http://localhost:2019/config/" | jq</span>
{ {
"apps": { "apps": {
"http": { "http": {
"servers": { "servers": {
"myserver": { "myserver": {
"listen": [ "listen": [
":443" ":443"
], ],
"routes": [ "routes": [
{ {
"match": [ "match": [
{ {
"host": [ "host": [
"example.com" "example.com"
] ]
} }
], ],
"handle": [ "handle": [
{ {
"handler": "file_server" "handler": "file_server"
} }
] ]
} }
] ]
} }
} }
} }
} }
}</code></pre> }</code></pre>
Export just the listener addresses: Export just the listener addresses:
@ -244,12 +244,12 @@ Returns information about a particular [PKI app](/docs/json/apps/pki/) CA by its
<pre><code class="cmd"><span class="bash">curl "http://localhost:2019/pki/ca/local" | jq</span> <pre><code class="cmd"><span class="bash">curl "http://localhost:2019/pki/ca/local" | jq</span>
{ {
"id": "local", "id": "local",
"name": "Caddy Local Authority", "name": "Caddy Local Authority",
"root_common_name": "Caddy Local Authority - 2022 ECC Root", "root_common_name": "Caddy Local Authority - 2022 ECC Root",
"intermediate_common_name": "Caddy Local Authority - ECC Intermediate", "intermediate_common_name": "Caddy Local Authority - ECC Intermediate",
"root_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... gRw==\n-----END CERTIFICATE-----\n", "root_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... gRw==\n-----END CERTIFICATE-----\n",
"intermediate_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... FzQ==\n-----END CERTIFICATE-----\n" "intermediate_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... FzQ==\n-----END CERTIFICATE-----\n"
}</code></pre> }</code></pre>

2
src/docs/markdown/automatic-https.md
View file

@ -179,7 +179,7 @@ The DNS challenge performs an authoritative DNS lookup for the candidate hostnam
This challenge does not require any open ports, and the server requesting a certificate does not need to be externally accessible. However, the DNS challenge requires configuration. Caddy needs to know the credentials to access your domain's DNS provider so it can set (and clear) the special TXT records. If the DNS challenge is enabled, other challenges are disabled by default. This challenge does not require any open ports, and the server requesting a certificate does not need to be externally accessible. However, the DNS challenge requires configuration. Caddy needs to know the credentials to access your domain's DNS provider so it can set (and clear) the special TXT records. If the DNS challenge is enabled, other challenges are disabled by default.
Since ACME CAs follow DNS standard when looking up TXT records for challenge verification, you can use CNAME records to delegate answering the challenge to other DNS zones. This can be used to delegate the `_acme-challenge` subdomain to another zone. This is particularly useful if your DNS provider doesn't provide an API, or isn't supported by one of the DNS plugins for Caddy. Since ACME CAs follow DNS standards when looking up TXT records for challenge verification, you can use CNAME records to delegate answering the challenge to other DNS zones. This can be used to delegate the `_acme-challenge` subdomain to another zone. This is particularly useful if your DNS provider doesn't provide an API, or isn't supported by one of the DNS plugins for Caddy.
DNS provider support is a community effort. [Learn how to enable the DNS challenge for your provider at our wiki.](https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148) DNS provider support is a community effort. [Learn how to enable the DNS challenge for your provider at our wiki.](https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148)