I’m not sure this belongs here, but I saw a previous issue
directed a request be opened here. With TLS certificate wildcard-ing in general and wildcard host matching for Routes within Kong already, this seems more an oversight than a new feature?
Regardless, requesting Kong allow wildcard matching of SNI values for TLS certificates when proxying request traffic. This will alleviate the need for enormous lists of SNI values for subdomains that are covered by a wildcard TLS certificate. Is there a reason to NOT support this (again, given that certificates support wildcards)?
Currently using Kong:0.14.0 - docker image with Postgres 9.5.