PowerDNS PDNS_API_URL API version issue #2016
Description
Welcome
- Yes, I'm using a binary release within 2 latest releases.
- Yes, I've searched similar issues on GitHub and didn't find any.
- Yes, I've included all information below (version, config, etc).
What did you expect to see?
Would lilke that lego accepts API version in PDNS_API_URL or to detect the version properly.
What did you see instead?
When 'PDNS_API_URL' is set to 'http://server/', without 'api/v1' prefix, API version is not detected and all pdns requests are made to / instead to /api/v1 so all PowerDNS requests fails.
When 'PDNS_API_URL' is set to 'http://server/api/v1' all pdns requests are made to /api/v1/api/v1. So version prefix is duplicated and again all PowerDNS request fails.
Why not just allow API version in URL?
Another project noticed the same issue - traefik/traefik#9726
How do you use lego?
Binary
Reproduction steps
- Install lego
- Configure PDNS_API_KEY and PDNS_API_URL with http://server or with http://server/api/v1
- Run
lego -a \
-d <domain> \
-m <e-mail> \
--server <ACME server if used > \
--dns pdns \
renew
Version of lego
lego version 4.14.0 darwin/arm64Logs
PDNS_API_URL=https://< server >/api/v1
...
<title>Error</title>
</head>
<body>
<pre>Cannot GET /api/v1/api</pre>
</body>
</html>
...PDNS_API_URL=https://< server >
...
<title>Error</title>
</head>
<body>
<pre>Cannot GET /api</pre>
</body>
</html>
...Go environment (if applicable)
No response