go-acme

go-acme copied to clipboard

Hi there, neat client!

Whenever I find a new ACME client I check the source to see if they're setting a user agent. This is really useful from a server operator perspective because it helps us identify misbehaving clients & understand the ecosystem from our request logs.

Section 6.1 of the ACME spec goes as far as to say clients SHOULD set a UA:

ACME clients SHOULD send a User-Agent header in accordance with [RFC7231], including the name and version of the ACME software in addition to the name and version of the underlying HTTP client software.

Would you consider adding a UA to go-acme? Thanks!

Hmm, weird I missed notification for this issue.

Just checked and it seemed to be quite some work to add custom header. Probably have to wait till next refactor to add UA. Besides, the tool is not widely used so far so the impact should be minimal :)

@riobard That's fair :-) thanks for considering!

I'll leave this issue open till I got some time to rewrite the stuff. Probably when the wildcard domain support kicks in next year (which requires dns-01 I think?). Kudos for the great work at LetsEncrypt.org! 👍