diff options
author | Wouter Tinus <win.acme.simple@gmail.com> | 2020-10-02 06:04:59 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-10-02 06:04:59 +0200 |
commit | 160ed1ad546b1a71d0d2a1557073b40983964bfe (patch) | |
tree | 1e8a1afd3ee2e75c6ee5e10306fc6df1696b1470 /docs/reference/plugins/installation/iisweb.md | |
parent | c662521de225e4dd4078fc6f0c2d1adfe323e368 (diff) | |
parent | f0390cc9d8d8ffe82c4641f1e09e06d1ca9e12ae (diff) | |
download | letsencrypt-win-simple-160ed1ad546b1a71d0d2a1557073b40983964bfe.zip letsencrypt-win-simple-160ed1ad546b1a71d0d2a1557073b40983964bfe.tar.gz letsencrypt-win-simple-160ed1ad546b1a71d0d2a1557073b40983964bfe.tar.bz2 |
Merge pull request #1672 from win-acme/2.1.11v2.1.11
2.1.11
Diffstat (limited to 'docs/reference/plugins/installation/iisweb.md')
-rw-r--r-- | docs/reference/plugins/installation/iisweb.md | 34 |
1 files changed, 0 insertions, 34 deletions
diff --git a/docs/reference/plugins/installation/iisweb.md b/docs/reference/plugins/installation/iisweb.md deleted file mode 100644 index c9d2cef..0000000 --- a/docs/reference/plugins/installation/iisweb.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -sidebar: reference ---- - -# IIS Web -Create or update website bindings in IIS, according to the following logic: - -- Existing https bindings in *any* site linked to the previous certificate are updated to use the new certificate. -- Hosts names which are determined to not yet have been covered by any existing binding, will be processed further. - - All existing https bindings in *target* site whose hostnames match with the new certificate are updated - to use the new certificate. This happens even if they are using certificates issued by other authorities. - (Note that if you want to prevent this from happening, you can use the `--excludebindings` switch). - - If no existing https binding can be found, a new binding is created. - - It will create bindings on the specified installation site and fall back to the target site if there is none. - - It will use port `443` on IP `*` unless different values are specified with the `--sslport` and/or - `--sslipaddress` switches. - - New bindings will be created or updated for matching host headers with the most specific match. E.g. if you - generate a certificate for `a.b.c.com`, the order of preference for the binding creation/change will be: - 1. `a.b.c.com` - 2. `*.b.c.com` - 3. `*.c.com` - 4. `*.com` - 5. `*` (Default/empty binding) - - If the certificate contains a wildcard domain, the order of preference will be: - 1. `*.a.b.c.com` - 2. `x.a.b.c.com` - - In both cases, the first preferred option will be created from scratch if none of the later options - are available. - - In some cases the plugin will not be able to (safely) add a new binding on older versions of IIS, e.g. due to - lack of support for SNI and/or wildcard bindings. In that case the user will have to create them manually. - Renewals will still be automatic after this initial manual setup. - -## Unattended -`--installation iis [--installationsiteid x] [-sslport x] [--sslipaddress x]`
\ No newline at end of file |