| commit | a521dfce2584b08efb1ec3eab94c05254dcf8f09 | [log] [tgz] |
|---|---|---|
| author | Alex Vaghin <ddos@google.com> | Sat Jul 21 22:26:40 2018 +0200 |
| committer | Alex Vaghin <ddos@google.com> | Mon Jul 23 16:08:21 2018 +0000 |
| tree | cc4697124f304b5a14e3744710f6ba0c9ac44d35 | |
| parent | a2144134853fc9a27a7b1e3eb4f19f1a76df13c9 [diff] |
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>
This repository holds supplementary Go cryptography libraries.
The easiest way to install is to run go get -u golang.org/x/crypto/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/crypto:” in the subject line, so it is easy to find.
Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.