Implement optional POST-as-GET support #3871
The draft ACME protocol has removed unauthenticated GET requests to order, authorization, and challenge resources. Because this is not a backwards compatible change we're intending to roll out support gradually before removing support for GETs to these resources entirely.
We need to:
On November 1st, 2019 we will remove support for GET requests to orders, authorizations and challenges making POST-as-GET mandatory. When we do this we'll need to take care that you can't access any V2 resources via the V1 endpoint.
Client developers that want a head-start testing their clients against this change are encouraged to use Pebble, which has already implemented the change for
The text was updated successfully, but these errors were encountered: