Niklas, When there are multiple kinds of rate limits affecting the current transaction, would you imagine that these headers should only illustrate the most restrictive? For example, Let's Encrypt has both "per-FQDN" and "per-Registered Domain" limits active now, each with a different state.
I'd like to avoid a meta-language inside the headers, certainly. I'd also like whatever we add to be useful. Perhaps there should be a "RateLimit-Name" header to define which limit is being described? - J.C. On Mon, Mar 21, 2016 at 2:34 AM, Niklas Keller <m...@kelunik.com> wrote: > > 2016-03-21 9:53 GMT+01:00 Philipp Junghannß <teamhydro55...@gmail.com>: >> >> adding to this some parts of rate limits should be maybe made a bit clearer >> if not already (e.g. if you have multiple different domains in a SAN which >> will get the count, just the CN? or all of them? >> also it would be nice to add a command that gives you the ability to check >> the limits before even thinking of creating a cert. > > > That's totally true, didn't think about that. I'll update the PR. > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme > _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
