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

Support POST-as-GET Requests, where indicated by RFC 8555 #26

Closed
glatzert opened this issue Apr 29, 2019 · 2 comments
Closed

Support POST-as-GET Requests, where indicated by RFC 8555 #26

glatzert opened this issue Apr 29, 2019 · 2 comments

Comments

@glatzert
Copy link
Collaborator

ACMEs RFC (https://tools.ietf.org/html/rfc8555#section-6.3 and following) defines some of the requests to be POST-as-GET.
We do not adhere to that everywhere and have to adjust to be compliant.

The CmdLets will be examined and corrected where neccessary.

@san360
Copy link

san360 commented May 13, 2019

FYI, Based on https://github.com/letsencrypt/boulder/blob/master/docs/acme-divergences.md

POST-as-GET: We support POST-as-GET but do not yet mandate it. We plan to mandate POST-as-GET for all ACMEv2 requests in late 2019.

@glatzert
Copy link
Collaborator Author

Closed via #37

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

2 participants