Graceful handling of badNonce error, retry with new nonce

[kellpossible]

https://github.com/letsencrypt/pebble?tab=readme-ov-file#invalid-anti-replay-nonce-errors

[kellpossible]

While it should be possible to handle at a higher level, it seems to me like something that could be a good candidate to handle inside the ACME client, as the error could present itself in many places.

[djc]

Sounds good, want to submit a PR? Retry up to 3 times with some backoff?

[kellpossible]

Hi! I don't have time at the moment unfortunately, but if it crops up in production I'm sure it will become a priority. Feel free to close, at least it's here for the record

…

On Mon, 12 Aug 2024, 17:33 Dirkjan Ochtman, ***@***.***> wrote: Sounds good, want to submit a PR? — Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCRJ2QP6HLPJK7BRSKDP7LZRBQK5AVCNFSM6AAAAABMLOV36CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBTGI4DGNRSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nick96]

I had a go at this in #65 because I ran into it trying to do some testing against pebble. Let me know what you think.