Alex Vaghin a521dfce25 acme: expect 202 Accepted from Let's Encrypt ...

ACME draft specifies the CA servers should respond
with 201 Created status code but Let's Encrypt
responds with 202 Accepted when creating a new account.

This change adds 202 Accepted as a valid response.
Otherwise, the Client hangs while doing retries,
discarding 202 responses as invalid.

Tests are not updated intentionally
due to this being non-conformant with the spec.

Fixes golang/go#26251

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

2018-07-23 16:08:21 +00:00

..

autocert

acme/autocert: surface details of acme.AuthorizationError

2018-06-14 20:24:12 +00:00

acme_test.go

acme: fix encoding of the TLS-ALPN challenge extension

2018-06-13 20:22:54 +00:00

acme.go

acme: expect 202 Accepted from Let's Encrypt

2018-07-23 16:08:21 +00:00

http_test.go

acme: consistently return original errors from retries

2018-06-21 12:51:26 +00:00

http.go

acme: consistently return original errors from retries

2018-06-21 12:51:26 +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: add support for TLS-ALPN

2018-06-08 09:28:29 +00:00