-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need rate limiting option for timestamp operations #249
Comments
Setting MDOP a lower value addressed this for us. This seems like something that will affect higher core count systems worse. Having an independent rate limit for the timestamping server requests v.s. the actual signing logic would be beneficial, so that work can be done more in parallel. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our timestamp provider for our certificate rate limits the number of requests, so after a few files (we're doing ~40 at a shot) are signed a few will fail with HTTP 429 and the rest succeed.
An option to rate limit or insert a delay between each signing request that uses timestamps would alleviate this issue.
The text was updated successfully, but these errors were encountered: