Wildcard Matching of Hostnames

The  supports wildcard matching of hostnames with HTTPS as defined in RFC 2818 (HTTP Over TLS). Wildcards can be of the form:
gateway83
The
API Gateway
 supports wildcard matching of hostnames with HTTPS as defined in RFC 2818 (HTTP Over TLS). Wildcards can be of the form:
*.domain.com
*.sub.domain.com
*.sub2.sub1.domain.com
Where the '
*
' character matches a domain component or part of the domain component, but not a subdomain.
Wildcard matching is disabled by default on the Gateway. To enable it, set the 
io.httpsHostAllowWildcard 
cluster property to "true".
Examples
:
*.domain.com
matches
host.domain.com
because
*
can represent
host
h*.domain.c
om matches
host.domain.com
because
*
can represent
ost
*t.domain.com
matches
host.domain.com
because
*
can represent
hos
host.*.domain.com
matches
host.sub.domain.com
because
*
can represent
sub
*.domain.com
does not match
host.sub.domain.com
because
*
cannot represent
host.sub
For LDAPS, POP3S, IMAPS, and SMTPS, the wildcard can only match the hostname, not any other component of the name, so for LDAPS:
host.*.domain.com
does not match
host.sub.domain.com
because
*
cannot represent
sub