[Acme] RFC 8555 challenge response proposal

Hello, Section 7.5.1 of RFC 8555 states the client sends an empty JSON body POST request to the challenge URL to confirm it's ready for validation. This seems, perhaps, overly restrictive, and certainly inefficient for authorization types that are able to produce a valid challenge response at the

[Acme] Re: RFC 8555 challenge response proposal

On Mon, Nov 11, 2024 at 12:38 PM Jeremy Hahn wrote: > Section 7.5.1 of RFC 8555 states the client sends an empty JSON body POST > request to the challenge URL to confirm it's ready for validation. This > seems, perhaps, overly restrictive, and certainly inefficient for > authorization types that

[Acme] Re: RFC 8555 challenge response proposal

On Mon, Nov 11, 2024 at 03:25:03PM -0500, Jeremy Hahn wrote: > Hello, > > Section 7.5.1 of RFC 8555 states the client sends an empty JSON body POST > request to the challenge URL to confirm it's ready for validation. This > seems, perhaps, overly restrictive, and certainly inefficient for > author