[FEATURE REQUEST]Muti-Domains TLS Support
- Dominant language
- Go
- Stars
- 25.6k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
I want use muti-domains bind to port 443 and use domain to defined the api service endpoint, in one domain like "domain.com" I can use wildcard cert to make subdomain support, however, I can not use muti-domain for TLS support.
Yes, maybe looked like a **TLS supported virtualhost, or a gateway-like service**.
For example:
> First, I want use iris to build my blog use **domain1.com**, this will taken my 80 and 443 ports left.
>
> Second, I want build another website in same server to show my product in domain **domain2.com**.
>
> If I want users can access my product website easily, I should reuse ports 80, 443, whatever, I don't think start a new iris service in other ports is a good idea, because user do not like type ports in domain normally.
**Describe the solution you'd like**
Support muti-domain TLS in one iris application.
**Describe alternatives you've considered**
* Make Nginx or Apache to be an agent support tls virtual host and proxy to service api.
* Use SNI to defined which domain accessed and return target domain certificate and make connection.
* Listen 80 and 443 in one iris application, then check host and redirect to target domain defined service with other ports(running other iris application).
**Additional context**
Nil
Contributor guide
Assessment
This issue has not been assessed yet.