James Hartig cbc3d0884e acme: automatically retry on badNonce errors ...

After receiving a badNonce error, the call can be safely retried. Nonce
errors can happen unexpectedly based on an unknown expiration date or
server-side changes. Rather than force the caller handle these errors,
retryPostJWS will keep retrying until success or a different error.

According to the spec, the error returned should be
"urn:ietf:params:acme:error:badNonce", but the error that Let's Encrypt
returns is "urn:acme:error:badNonce" so we just check the suffix.

Fixes golang/go#19703

Change-Id: Id15012dff91e51d28ed8bc54f13a6212186cb7df
Reviewed-on: https://go-review.googlesource.com/40130
Run-TryBot: Alex Vaghin <ddos@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Alex Vaghin <ddos@google.com>

2017-04-13 18:22:23 +00:00

..

autocert

acme/autocert: fix context usage

2017-04-12 07:03:28 +00:00

acme_test.go

acme: automatically retry on badNonce errors

2017-04-13 18:22:23 +00:00

acme.go

acme: automatically retry on badNonce errors

2017-04-13 18:22:23 +00:00

jws_test.go

acme: expose internal/acme as acme package

2016-08-31 19:38:21 +00:00

jws.go

acme: expose internal/acme as acme package

2016-08-31 19:38:21 +00:00

types.go

acme: expose internal/acme as acme package

2016-08-31 19:38:21 +00:00