Originally created by @rnz on GitHub (Jun 5, 2019).
In hook domain.txt:
domain.name *.domain.name > cert_domain.name
but hook run twice domain_challenge with: domain.name
...
case "$1" in
"deploy_challenge")
echo "domain: $2"
...
Originally created by @rnz on GitHub (Jun 5, 2019).
In hook domain.txt:
domain.name *.domain.name > cert_domain.name
but hook run twice domain_challenge with: domain.name
```
...
case "$1" in
"deploy_challenge")
echo "domain: $2"
...
```
Wild card domain validation is performed on the domain name WITHOUT the wild card specified. So if you are validating ".domain.name" then the deploy_challenge hook will be instructed to deploy a challenge for "domain.name". In your example this will appear initially as an attempt to deploy a challenge for "domain.name" twice, once for "domain.name" and once for ".domain.name"
@jobe1986 commented on GitHub (Jun 5, 2019):
Wild card domain validation is performed on the domain name WITHOUT the wild card specified. So if you are validating "*.domain.name" then the deploy_challenge hook will be instructed to deploy a challenge for "domain.name". In your example this will appear initially as an attempt to deploy a challenge for "domain.name" twice, once for "domain.name" and once for "*.domain.name"
Like @jobe1986 said wildcard domains are validated using the upper level domain. If you need information about what domains your hook is validating you can use the altnames variable.
@lukas2511 commented on GitHub (Aug 15, 2019):
Like @jobe1986 said wildcard domains are validated using the upper level domain. If you need information about what domains your hook is validating you can use the altnames variable.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rnz on GitHub (Jun 5, 2019).
In hook domain.txt:
domain.name *.domain.name > cert_domain.name
but hook run twice domain_challenge with: domain.name
@jobe1986 commented on GitHub (Jun 5, 2019):
Wild card domain validation is performed on the domain name WITHOUT the wild card specified. So if you are validating ".domain.name" then the deploy_challenge hook will be instructed to deploy a challenge for "domain.name". In your example this will appear initially as an attempt to deploy a challenge for "domain.name" twice, once for "domain.name" and once for ".domain.name"
@lukas2511 commented on GitHub (Aug 15, 2019):
Like @jobe1986 said wildcard domains are validated using the upper level domain. If you need information about what domains your hook is validating you can use the altnames variable.