Re:Scaling the Let's Encrypt rate limits to prepare for a bi...
by altairprime on Monday May 26, 2025 @12:46PM
(#44099085)
> Conveniently, the difference between the TAT and the current time can then be returned to the subscriber in a Retry-After header, informing their client exactly how long to wait before trying again.
I hope they know to add in a small amount of anti-synchronization randomness to the exactly-calculated “retry-after” delay.
I hope they know to add in a small amount of anti-synchronization randomness to the exactly-calculated “retry-after” delay.