mirror of
https://github.com/caddyserver/caddy.git
synced 2025-02-05 16:48:27 +03:00
6ca5828221
Certificate selection used to be a module, but this seems unnecessary, especially since the built-in CustomSelectionPolicy allows quite complex selection logic on a number of fields in certs. If we need to extend that logic, we can, but I don't think there are SO many possibilities that we need modules. This update also allows certificate selection to choose between multiple matching certs based on client compatibility and makes a number of other improvements in the default cert selection logic, both here and in the latest CertMagic. The hardest part of this was the conn policy consolidation logic (Caddyfile only, of course). We have to merge connection policies that we can easily combine, because if two certs are manually loaded in a Caddyfile site block, that produces two connection policies, and each cert is tagged with a different tag, meaning only the first would ever be selected. So given the same matchers, we can merge the two, but this required improving the Tag selection logic to support multiple tags to choose from, hence "tags" changed to "any_tag" or "all_tags" (but we use any_tag in our Caddyfile logic). Combining conn policies with conflicting settings is impossible, so that should return an error if two policies with the exact same matchers have non-empty settings that are not the same (the one exception being any_tag which we can merge because the logic for them is to OR them). It was a bit complicated. It seems to work in numerous tests I've conducted, but we'll see how it pans out in the release candidates. |
||
|---|---|---|
| .. | ||
| distributedstek | ||
| standardstek | ||
| acmeissuer.go | ||
| automation.go | ||
| certselection.go | ||
| connpolicy.go | ||
| fileloader.go | ||
| folderloader.go | ||
| internalissuer.go | ||
| matchers.go | ||
| matchers_test.go | ||
| pemloader.go | ||
| sessiontickets.go | ||
| tls.go | ||
| values.go | ||