Closed jsha closed 4 years ago
@serverco-a @timkimber @EmiiKhaos Do you folks think it might be possible to address this before a new release is cut with the recently merged ACME v2 support? I think that new code is going to prompt a lot of users to update their getssl installations and I'd love to see them send a UA on day 1 of using the V2 API.
Just done a PR to address this issue - just need @serverco-a or @EmiiKhaos to review it
I've been looking at Let's Encrypt logs, and I notice a number of entries that just have User-Agent: curl/x.y.z. It looks like getssl doesn't currently set this header explicitly. It would be really helpful if it did! Here's what the ACME RFC has to say on User-Agent:
https://tools.ietf.org/html/rfc8555#page-10
Thanks, Jacob