From 92d9569bc9785a6906575bed77a83cbe88f14323 Mon Sep 17 00:00:00 2001 From: Felix Fontein Date: Mon, 29 Oct 2018 10:32:53 +0100 Subject: ACME: add support for POST-as-GET if GET fails with 405. (#44988) * Add support for POST-as-GET if GET fails with 405. * Bumping ACME test container version to 1.4. This includes letsencrypt/pebble#162 and letsencrypt/pebble#168. * Also use POST-as-GET for account data retrival. This is not yet supported by any ACME server (see letsencrypt/pebble#171), so we fall back to a regular empty update if a 'malformedRequest' error is returned. * Using newest ACME test container image. Includes letsencrypt/pebble#171 and letsencrypt/pebble#172, which make Pebble behave closer to the current specs. * Remove workaround for old Pebble version. * Add changelog entry. * First try POST-as-GET, then fall back to unauthenticated GET. --- changelogs/fragments/44988-acme-post-as-get.yaml | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 changelogs/fragments/44988-acme-post-as-get.yaml (limited to 'changelogs') diff --git a/changelogs/fragments/44988-acme-post-as-get.yaml b/changelogs/fragments/44988-acme-post-as-get.yaml new file mode 100644 index 0000000000..f2968fd6df --- /dev/null +++ b/changelogs/fragments/44988-acme-post-as-get.yaml @@ -0,0 +1,2 @@ +bugfixes: +- "ACME modules support `POST-as-GET `__ and will be able to access Let's Encrypt ACME v2 endpoint after November 1st, 2019." -- cgit v1.2.1