Alex Vaghin df8d4716b3 acme: clarify retries and backoff algorithm ...

There's been some confusion about failed request retries.
Rightfully so: some requests are retried, others are not.

This change attempts to clarify the issue and unify backoff
usage in all Client's methods by introducing a new exported
optional field RetryBackoff and adding retry logic where missing.

Also, updates golang/go#22457.

Change-Id: Ied434edf998d52925a48b6b3b2407d45a6e9d2ee
Reviewed-on: https://go-review.googlesource.com/109615
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

2018-06-02 22:01:24 +00:00

..

autocert

acme/autocert: improve authorizations cleanup

2018-05-27 07:24:34 +00:00

acme_test.go

acme: clarify retries and backoff algorithm

2018-06-02 22:01:24 +00:00

acme.go

acme: clarify retries and backoff algorithm

2018-06-02 22:01:24 +00:00

http_test.go

acme: clarify retries and backoff algorithm

2018-06-02 22:01:24 +00:00

http.go

acme: clarify retries and backoff algorithm

2018-06-02 22:01:24 +00:00

jws_test.go

acme: generate correct ES512 signatures

2017-04-25 15:34:59 +00:00

jws.go

acme: generate correct ES512 signatures

2017-04-25 15:34:59 +00:00

types_test.go

acme: add function to check rate limits

2017-04-25 18:26:15 +00:00

types.go

acme: clarify retries and backoff algorithm

2018-06-02 22:01:24 +00:00