Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid hardcoded URIs #1

Closed
alexpeattie opened this issue Mar 30, 2016 · 1 comment
Closed

Avoid hardcoded URIs #1

alexpeattie opened this issue Mar 30, 2016 · 1 comment

Comments

@alexpeattie
Copy link
Owner

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 (?).

Improvement suggested by @kelunik

alexpeattie added a commit that referenced this issue Nov 19, 2016
…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
@alexpeattie
Copy link
Owner Author

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 🎉 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant