letsencrypt
/
boulder
mirror of https://github.com/letsencrypt/boulder.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: boulder now has Retry-After on all ratelimits (#7876) 

Thanks to MikeMcQ from the forum for
[noticing](https://community.letsencrypt.org/t/new-rate-limit-page-in-conflict-with-boulder-variances/229849).
This commit is contained in:
Jacob Hoffman-Andrews 2024-12-12 13:27:58 -08:00 committed by GitHub
parent 1ddd4633f5
commit efaa370457
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/acme-divergences.md
View File

@ -9,10 +9,6 @@ Presently, Boulder diverges from the [RFC 8555] ACME spec in the following ways:
Boulder supports POST-as-GET but does not mandate it for requests
that simply fetch a resource (certificate, order, authorization, or challenge).
## [Section 6.6](https://tools.ietf.org/html/rfc8555#section-6.6)
For all rate-limits, Boulder includes a `Link` header to additional documentation on rate-limiting. Only rate-limits on `duplicate certificates` and `certificates per registered domain` are accompanied by a `Retry-After` header.
## [Section 7.1.2](https://tools.ietf.org/html/rfc8555#section-7.1.2)
Boulder does not supply the `orders` field on account objects. We intend to