mirror of
https://github.com/caddyserver/caddy.git
synced 2024-12-23 22:27:38 -05:00
7bd2adf0dc
If Caddy is running but not listening on port 80, reloading Caddy with a new Caddyfile that needs to obtain a TLS cert from the CA would fail, because it was just assumed that, if reloading, port 80 as already in use. That is not always the case, so we scan the servers to see if one of them is listening on port 80, and we configure the ACME client accordingly. Kind of a hack... but it works. |
||
|---|---|---|
| .. | ||
| assets | ||
| caddyfile | ||
| https | ||
| parse | ||
| setup | ||
| caddy.go | ||
| caddy_test.go | ||
| config.go | ||
| config_test.go | ||
| directives.go | ||
| directives_test.go | ||
| helpers.go | ||
| restart.go | ||
| restart_windows.go | ||
| sigtrap.go | ||
| sigtrap_posix.go | ||
| sigtrap_windows.go | ||