Commit graph

6 commits

Author SHA1 Message Date
Remi Broemeling
2e0e9cd68f Slightly improve Dyn provider error reporting. (#473)
If Dyn responds with a 3xx or 4xx status code, information describing exactly
what went wrong is generally included in the body of the response (as part of
the typical Dyn JSON response). On the other hand, if Dyn responds with a 5xx
status code, we very likely have extremely limited information.

This commit modifies the reporting to display the explanatory messages included
in the body of the Dyn response for 3xx and 4xx status codes. The intent is to
make it much easier to determine what might be going wrong (when something is
going wrong).
2018-03-19 10:41:57 -06:00
Andrew E. Bruno
ecf664eaef Fixes #199
Dyn provider was using incorrect zone in Present and Cleanup functions.
This uses FindZoneByFqdn() to find the correct zone for use in the
subsequent API calls.
2016-04-26 22:36:48 -04:00
Brett Vickers
47219adc00 Make DNS provider credential-handling more consistent.
Different DNS providers were handling credentials in different ways.
Some were reading credential environment variables in cli_handlers.go
and then passing them into the NewDNSProvider function, while others
were reading the environment variables within their NewDNSProvider
functions.

This change replaces each DNS challenge's NewDNSProvider function with
two new functions: (1) a NewDNSProvider function that takes no
parameters and uses the environment to read credentials, and (2) a
NewDNSProviderCredentials that takes credentials as parameters.
2016-03-20 11:40:30 -07:00
Andrew E. Bruno
b10c35bba1 golint fixes.
- dynRequest should be private to dyn package
- Fix JobID name
2016-03-19 16:14:23 -04:00
Andrew E. Bruno
9f8d5e4076 Add timeout to HTTP client 2016-03-18 23:20:58 -04:00
Andrew E. Bruno
1de97a90da Move dyn provider out of acme package per #144 2016-03-17 22:30:21 -04:00