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
Use the directory (https://acme-v01.api.letsencrypt.org/directory) to get the new-* URIs, the up link in the new-cert response, and the headers of the new-reg for the agreement URL (?).
…ments
* Use the directory and response headers, rather than hardcoding URIs (closes [#1](#1))
* Add Appendix 6 about newly supported Internationalized Domain Names
* Change reference to official Let's Encrypt client → certbot
* Specify a TTL for DNS challenge record
* Add note about certificate and authorization validity periods
* Consistently prefer single quotes in all Ruby code
* Remove example domains for the various certificate types
* Added a couple more tools to the Testing section
* Add Changelog & Author section
* Harden example nginx config with additional security headers
I ended up falling down a bit of a rabbit hole with this 🐰🕳 and had to write my own gem to parse Link headers. But the guide's all updated now, and no longer uses any hardcoded URIs, except for the directory 🎉 .
Use the directory (https://acme-v01.api.letsencrypt.org/directory) to get the
new-*
URIs, theup
link in thenew-cert
response, and the headers of thenew-reg
for the agreement URL (?).Improvement suggested by @kelunik
The text was updated successfully, but these errors were encountered: