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

docs: default_bind option

Browse source
This commit is contained in:
Francis Lavoie 2022-03-09 03:40:43 -05:00
parent 9f35c4fe2d
commit 2581eba019
No known key found for this signature in database
GPG key ID: E73DB3ECE64E7885
1 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -42,8 +42,9 @@ Possible options are:
{ {
# General Options # General Options
debug debug
http_port <port> http_port <port>
https_port <port> https_port <port>
default_bind <host>
order <dir1> first|last|[before|after <dir2>] order <dir1> first|last|[before|after <dir2>]
storage <module_name> { storage <module_name> {
<options...> <options...>
@ -142,6 +143,10 @@ The port for the server to use for HTTP. For internal use only; does not change
The port for the server to use for HTTPS. For internal use only; does not change the HTTPS port for clients. Default: `443` The port for the server to use for HTTPS. For internal use only; does not change the HTTPS port for clients. Default: `443`
##### `default_bind`
The default bind address to be used for all sites, if the [`bind` directive](/docs/caddyfile/directives/bind) is not used in the site. Default: empty, which binds to all interfaces.
##### `order` ##### `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. 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.