mirror of
https://github.com/caddyserver/website.git
synced 2025-04-24 22:16:15 -04:00
docs: More changes for upcoming v2.5.0 release (#226)
This commit is contained in:
parent
35a02d78d7
commit
eaf0aae816
6 changed files with 73 additions and 8 deletions
|
@ -29,6 +29,8 @@ map [<matcher>] <source> <destinations...> {
|
|||
|
||||
As a special case, the Caddyfile parser treats outputs that are a literal hyphen (`-`) as null/nil values. This is useful if you want to fall back to a default value for that particular output in the case of the given input, but want to use non-default values for other outputs.
|
||||
|
||||
The outputs will be type converted if possible; `true` and `false` will be converted to boolean types, and numeric values will be converted to integer or float accordingly. To avoid this conversion, you may wrap the output with [quotes](/docs/caddyfile/concepts#tokens-and-quotes) and they will stay strings.
|
||||
|
||||
The number of outputs for each mapping must not exceed the number of destinations; however, for convenience, there may be fewer outputs than destinations, and any missing outputs will be filled in implicitly.
|
||||
|
||||
If a regular expression was used as the input, then the capture groups can be referenced with `${group}` where `group` is either the name or number of the capture group in the expression. Capture group `0` is the full regexp match, `1` is the first capture group, `2` is the second capture group, and so on.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue