mirror of
https://github.com/caddyserver/caddy.git
synced 2024-12-23 22:27:38 -05:00
4462e3978b
Original feature request in forum: https://forum.caddyserver.com/t/caddy-with-specific-hosts-but-on-demand-tls/1704?u=matt Before, Caddy obtained certificates for every name it could at startup. And it would only obtain certificates during the handshake for sites defined with a hostname that didn't qualify at startup (like "*.example.com" or ":443"). This made sense for most situations, and helped ensure that certificates were obtained as early and reliably as possible. With this change, Caddy will NOT obtain certificates for hostnames it knows at startup (even if they qualify) if OnDemand is enabled. But I think this change generalizes well, because a user who specifies max_certs is deliberately turning on On-Demand TLS, fully aware of the consequences. It seems dubious to ignore that config when the user deliberately put it there. We'll see how this goes. |
||
|---|---|---|
| .. | ||
| basicauth | ||
| bind | ||
| browse | ||
| errors | ||
| expvar | ||
| extensions | ||
| fastcgi | ||
| gzip | ||
| header | ||
| httpserver | ||
| index | ||
| internalsrv | ||
| log | ||
| markdown | ||
| maxrequestbody | ||
| mime | ||
| pprof | ||
| proxy | ||
| push | ||
| redirect | ||
| rewrite | ||
| root | ||
| staticfiles | ||
| status | ||
| templates | ||
| timeouts | ||
| websocket | ||
| caddyhttp.go | ||
| caddyhttp_test.go | ||