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

Update options.md

Browse source
This commit is contained in:
Aaron Paterson 2024-10-10 00:41:01 -04:00 • committed by GitHub
parent fe713a3429
commit f0e45f6a87
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 15 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

17
src/docs/markdown/caddyfile/options.md
View file

@ -194,7 +194,7 @@ Default: `443`
##### `default_bind`
The default bind address(es) and the HTTP protocol(s) to serve with them for all sites, if the [`bind` directive](/docs/caddyfile/directives/bind) is not used in the site. Default: empty, which binds to all interfaces, and serves the default protocols (h1+h2+h3) on them.
The default bind address(es) and the HTTP protocol(s) to serve with them for all sites, if the [`bind` directive](/docs/caddyfile/directives/bind) is not used in the site. If multiple `default_bind` directives are present, each will be applied to servers with no `bind` directive sequentially. Default: empty, which binds to all interfaces, and serves the default protocols (h1+h2+h3) on them.
<aside class="tip">
@ -210,7 +210,7 @@ For example, to bind to `10.0.0.1` when no other address(es) are specified:
}
```
or to disable HTTP/3 unless otherwise specified:
to disable HTTP/3 unless otherwise specified:
```caddy
{
@ -220,6 +220,19 @@ or to disable HTTP/3 unless otherwise specified:
}
```
to create listeners from file descriptors given by [environment placeholders](/docs/conventions#placeholders):
```caddy
{
default_bind fd/{env.CADDY_HTTPS_FD} {
protocols h1 h2
}
default_bind fdgram/{env.CADDY_HTTP3_FD} {
protocols h3
}
}
```
##### `order`
Assigns an order to HTTP handler directive(s). As HTTP handlers execute in a sequential chain, it is necessary for the handlers to be executed in the right order. Standard directives have [a pre-defined order](/docs/caddyfile/directives#directive-order), but if using third-party HTTP handler modules, you'll need to define the order explicitly by either using this option or placing the directive in a [`route` block](/docs/caddyfile/directives/route). Ordering can be described absolutely (`first` or `last`), or relatively (`before` or `after`) to another directive.