From b6d6247e1d4a195d44cfd286a7e7dd01e38bfed0 Mon Sep 17 00:00:00 2001 From: felixfontein Date: Tue, 30 Apr 2024 07:41:47 +0000 Subject: [PATCH] deploy: 6d4fc589aee55b81bb0717eed6dd12401785f20c --- pr/739/acme_certificate_module.html | 3 ++- pr/739/searchindex.js | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/pr/739/acme_certificate_module.html b/pr/739/acme_certificate_module.html index 81e3b004..8754f88e 100644 --- a/pr/739/acme_certificate_module.html +++ b/pr/739/acme_certificate_module.html @@ -422,9 +422,10 @@ see added in community.crypto 2.20.0

Determines whether to request renewal of an existing certificate according to the ACME ARI draft 3.

-

This is only used if the certificate specified in dest or fullchain_dest already exists.

+

This is only used when the certificate specified in dest or fullchain_dest already exists.

never never sends the certificate ID of the certificate to renew. always will always send it.

when_ari_supported only sends the certificate ID if the ARI endpoint is found in the ACME directory.

+

Generally you should use when_ari_supported if you know that the ACME service supports a compatible draft (or final version, once it is out) of the ARI extension. always should never be necessary. If you are not sure, or if you receive strange errors on invalid replaces values in order objects, use never, which also happens to be the default.

Choices: