Herman Slatman 1c38113e44 Add ACME Subproblem for more detailed ACME client-side errors ... When validating an ACME challenge (`device-attest-01` in this case, but it's also true for others), and validation fails, the CA didn't return a lot of information about why the challenge had failed. By introducing the ACME `Subproblem` type, an ACME `Error` can include some additional information about what went wrong when validating the challenge. This is a WIP commit. The `Subproblem` isn't created in many code paths yet, just for the `step` format at the moment. Will probably follow up with some more improvements to how the ACME error is handled. Also need to cleanup some debug things (q.Q)		2023-01-26 13:29:31 +01:00
..
account.go	Standardize linting file and fix or ignore lots of linting errors	2022-09-20 16:35:41 -07:00
account_test.go	Standardize linting file and fix or ignore lots of linting errors	2022-09-20 16:35:41 -07:00
eab.go	Standardize linting file and fix or ignore lots of linting errors	2022-09-20 16:35:41 -07:00
eab_test.go	Standardize linting file and fix or ignore lots of linting errors	2022-09-20 16:35:41 -07:00
handler.go	Add ACME Subproblem for more detailed ACME client-side errors	2023-01-26 13:29:31 +01:00
handler_test.go	Remove charset=utf-8 from ACME certificate requests	2022-11-09 19:57:50 +01:00
middleware.go	all: reformat all go files with the next gofmt (Go 1.19)	2022-06-16 01:28:59 +07:00
middleware_test.go	Standardize linting file and fix or ignore lots of linting errors	2022-09-20 16:35:41 -07:00
order.go	Add attestation certificate validation for Apple devices	2022-09-20 18:51:43 -07:00
order_test.go	Add AuthorizeChallenge unit tests	2022-09-20 19:03:03 -07:00
revoke.go	Fix panic in acme/api tests.	2022-05-02 17:35:35 -07:00
revoke_test.go	Merge branch 'master' into context-authority	2022-05-06 13:21:41 -07:00