greenlock.js/lib
AJ ONeal c8b895633c Fix regression with set challenges being ignored
Backwards compatibility madness.
When you Greenlock.create({ }), challenges will be set by default if
not available.  This is good... ish.

When you approveDomains() and set opts.challenges, however, those must
be able to override the defaults.

This was just recently broken and the fix seems to be to make the prior
defaults inaccessible, otherwise it becomes really confusing as to why
a set DNS challenge for local, wild, or private domains is not being
preferred to the (failing) http.

All this crap will be cleaned up in v3...
2019-06-14 03:21:03 -06:00
..
community.js add telemetry 2018-11-05 11:10:22 -07:00
compat.js v2.7.23: regression bugfixes: node v6 and cloudflare dns-01 2019-06-03 09:13:09 +00:00
core.js Fix regression with set challenges being ignored 2019-06-14 03:21:03 -06:00
middleware.js update for upcoming v3 2019-04-05 19:45:24 -06:00
utils-test.js v2.6.10: updates for simpler store plugin 2019-04-01 00:36:59 -06:00
utils.js Fix regression with set challenges being ignored 2019-06-14 03:21:03 -06:00