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

docs: Numerous various updates for v2.1

Browse source
This commit is contained in:
Matthew Holt 2020-06-08 14:56:20 -06:00
parent 148176582d
commit db18a5d4c8
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
9 changed files with 79 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -93,7 +93,7 @@ redir /old.html /new.html
Path matcher tokens must start with a forward slash `/`.
[Path matching](/docs/caddyfile/matchers#path) is an exact match by default; you must append a `*` for a fast prefix match. Note that `/foo*` will match `/foo` and `/foo/` as well as `/foobar`; you might actually want `/foo/*` instead.
**[Path matching](/docs/caddyfile/matchers#path) is an exact match by default;** you must append a `*` for a fast prefix match. Note that `/foo*` will match `/foo` and `/foo/` as well as `/foobar`; you might actually want `/foo/*` instead.
### Named matchers
@ -135,8 +135,6 @@ If the matcher set consists of only one matcher, a one-liner syntax also works:
reverse_proxy @post localhost:6001
```
(One-liner named matchers cannot open a block.)
Like directives, named matcher definitions must go inside the site blocks that use them.
A named matcher definition constitutes a _matcher set_. Matchers in a set are AND'ed together; i.e. all must match. For example, if you have both a `header` and `path` matcher in the set, both must match.