You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-3Lines changed: 17 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# ACMECert v3.6.0
1
+
# ACMECert v3.7.0
2
2
3
3
PHP client library for [Let's Encrypt](https://letsencrypt.org/) and other [ACME v2 - RFC 8555](https://tools.ietf.org/html/rfc8555) compatible Certificate Authorities.
4
4
@@ -23,6 +23,7 @@ It is self contained and contains a set of functions allowing you to:
23
23
-[parse certificates](#acmecertparsecertificate) / get the [remaining days](#acmecertgetremainingdays) or [percentage](#acmecertgetremainingpercent) a certificate is still valid
>> When issuing certificates using the `dns-01` challenge for multiple domains that share the same `_acme-challenge` subdomain, such as:
758
+
>> - example.com
759
+
>> - *.example.com (wildcard)
760
+
>>
761
+
>> two distinct TXT records must be created under the same DNS name `_acme-challenge.example.com`
762
+
>>
763
+
>> By default, ACMECert groups these challenges together. This means all required TXT records for `_acme-challenge.example.com` are set simultaneously, and validation is triggered only after all records are in place. This approach prevents validation failures due to DNS caching delays.
764
+
>>
765
+
>> If set to `FALSE` challenges are handled independently. Each TXT record gets set and validated one at a time.
0 commit comments