Thanks James - definitely an interesting case. I'd be sorry to see ACME and other APIs go down the route of POSTing base64 encoded blobs for all API interactions.
On Mon, 3 Sep 2018 at 14:56, Manger, James <james.h.man...@team.telstra.com> wrote: > ACME <https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html> > (Automatic Certificate Management Environment) [draft-ietf-acme-acme] (eg > Lets Encrypt CA) is an interesting case. It POSTs JWS objects using the > Flattened JSON Serialization with a "url" member in the protected header. > It is likely to use the same scheme (POST a JWS) to replace GET methods as > well. > > > > -- > > James Manger > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
