mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-04-23 05:26:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: Minor tweaks, clarifications.

Browse source
This commit is contained in:
Matthew Holt 2020-04-01 11:09:26 -06:00
parent 3ecf039665
commit 836e15afbc
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
4 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
src/docs/markdown/caddyfile/concepts.md
View file

@ -154,6 +154,8 @@ These are examples of valid addresses:
- `127.0.0.1`
- `[::1]:2015`
- `example.com/foo/*`
- `*.example.com`
- `http://`
<aside class="tip">
<a href="/docs/automatic-https">Automatic HTTPS</a> is enabled if your site's address contains a hostname or IP address. This behavior is purely implicit, however, so it never overrides any explicit configuration. For example, if the site's address is <code>http://example.com</code>, auto-HTTPS will not activate because the scheme is explicitly <code>http://</code>.
@ -163,6 +165,8 @@ From the address, Caddy can potentially infer the scheme, host, port, and path o
If you specify a hostname, only requests with a matching Host header will be honored. In other words, if the site address is `localhost`, then Caddy will not match requests to `127.0.0.1`.
Wildcards (`*`) may be used, but only to represent precisely one label of the hostname. For example, `*.example.com` matches `foo.example.com` but not `foo.bar.example.com`, and `*` matches `localhost` but not `example.com`. To catch all hosts, omit the host portion of the address.
If multiple sites share the same definition, you can list all of them together:
```