mirror of
https://github.com/caddyserver/caddy.git
synced 2024-12-16 21:56:40 -05:00
b3d35a4995
If an email is specified in global options, a site called 'localhost' shouldn't be bunched together with public DNS names in the automation policies, which get the default, public-CA issuers. Fix old test that did this.
I also noticed that these two:
localhost {
}
example.com {
}
and
localhost, example.com {
}
produce slightly different TLS automation policies. The former is what the new test case covers, and we have logic that removes the empty automation policy for localhost so that auto-HTTPS can implicitly create one. (We prefer that whenever possible.) But the latter case produces two automation policies, with the second one being for localhost, with an explicit internal issuer. It's not wrong, just more explicit than it needs to be.
I'd really like to completely rewrite the code from scratch that generates automation policies, hopefully there is a simpler, more correct algorithm.
|
||
|---|---|---|
| .. | ||
| addresses.go | ||
| addresses_fuzz.go | ||
| addresses_test.go | ||
| builtins.go | ||
| builtins_test.go | ||
| directives.go | ||
| directives_test.go | ||
| httptype.go | ||
| httptype_test.go | ||
| options.go | ||
| options_test.go | ||
| pkiapp.go | ||
| serveroptions.go | ||
| tlsapp.go | ||
| tlsapp_test.go | ||