Skip to content

Conversation

@adaugherity
Copy link
Contributor

Split off from #859; I believe this is a separate bug which still exists:

Another potential bug is the checking of the Replay-Nonce header. I noticed in the certbot debug log (which was successful) that Sectigo was sending a lowercase replay-nonce header.

It appears that further down it does use grep -i, so in effect it's just causing an initial "bad nonce" and will succeed on retry, but we may as well fix the first attempt.

@adaugherity
Copy link
Contributor Author

I can confirm that running this branch with the config in #883 does indeed eliminate the first badNonce response; it goes straight to externalAccountRequired.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a bug where getssl fails to extract the Replay-Nonce header when ACME servers (specifically Sectigo) send it in lowercase. The fix makes the header matching case-insensitive, which is the correct behavior according to HTTP standards (RFC 7230).

Changes:

  • Added -i flag to two grep commands that extract the Replay-Nonce header from ACME server responses

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@timkimber timkimber merged commit 05dbb09 into srvrco:master Jan 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants