certificates/acme
David Cowden 089e3aea4f acme/challenge: Fix error return type on KeyAuthorization
In golang, one should always return error types rather than interfaces
that conform to an error protocol. Why? Because of this:

    https://play.golang.org/p/MVa5vowuNRo

Feels ~~like JavaScript~~ bad, man.
2020-05-11 21:30:50 -07:00
..
api acme/api: Add missing return 2020-05-11 21:22:40 -07:00
account.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
account_test.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
authority.go acme/authority: Polymorph the challenge type 2020-05-11 21:23:55 -07:00
authority_test.go Add automated challenge retries, RFC 8555 2020-04-30 04:44:08 -07:00
authz.go acme: Retry challenge validation attempts 2020-05-06 07:39:13 -07:00
authz_test.go Add support for TLS-ALPN-01 challenge. 2020-02-07 14:37:13 -05:00
certificate.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
certificate_test.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
challenge.go acme/challenge: Fix error return type on KeyAuthorization 2020-05-11 21:30:50 -07:00
challenge_test.go Add automated challenge retries, RFC 8555 2020-04-30 04:44:08 -07:00
common.go acme: Retry challenge validation attempts 2020-05-06 07:39:13 -07:00
directory.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
directory_test.go wip 2019-09-19 13:17:45 -07:00
errors.go Should be returning status code 400 for ACME Account Not Found. 2020-02-01 17:35:41 -08:00
nonce.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
nonce_test.go Add ACME CA capabilities 2019-09-13 15:48:33 -07:00
order.go Add the commonName as a DNSName to match RFC. 2020-01-28 15:34:01 -08:00
order_test.go Add support for TLS-ALPN-01 challenge. 2020-02-07 14:37:13 -05:00