aboutsummaryrefslogtreecommitdiffstats
path: root/letsencrypt
diff options
context:
space:
mode:
authorGuilhem Moulin <guilhem@fripost.org>2023-04-25 10:51:36 +0200
committerGuilhem Moulin <guilhem@fripost.org>2023-04-25 11:11:03 +0200
commit53238c70f7a12e233a6ca83cf2b50168e5b9592e (patch)
tree58c0a8613062102f847d761d2c6836f74869075e /letsencrypt
parentb3af3526b293f396da02a6276ea86ca17dcd2d03 (diff)
client: Handle "ready" → "processing" → "valid" status change during newOrder.
Instead of just "ready" → "valid", which may be what we observe when the server is fast enough, but according to RFC 8555 sec. 7.1.6 the state actually transitions via "processing" state and we need to account for that. It appears Let's Encrypt staging environment now has different timing conditions and lacme is unable to request certificates due to this issue. Thanks to Alexander Borkowski for the report!
Diffstat (limited to 'letsencrypt')
0 files changed, 0 insertions, 0 deletions