v2.8.0: Fix regression with set challenges being ignored #40
已手动合并
coolaj86
于 5 年前 将 1 次代码提交从 dns-challenge-regression-fix
合并至 master
正在加载...
在新工单中引用
这个人很懒,什么都没留下。
删除分支 'dns-challenge-regression-fix'
删除分支是永久的。此操作 无法 撤销,继续?
Regression Fix
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...
New Feature
Oh, and this adds support for
getZones()
, the testing of which brought about the need to fix the regression.Fix regression with set challenges being ignored为 v2.8.0: Fix regression with set challenges being ignoredc8b895633c