-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST]Muti-Domains TLS Support #1690
Comments
Hello @Little-YangYang, I think it's better to use Nginx or Caddy for that scenarios but if you just want two Iris application running under the same process with two different subdomains/domains on the same host:port, you may want to check out the apps package or/and the rewrite middleware. Waiting for your response. |
Hello @kataras , thank you for your reply, if I use apps , is there any method to defined tls certificate for each application alone? |
But you wanted one certificate for all domains, right? If not, TLS certificates can only be registered per listener, there is an alternative of constructing a custom GetCertificate function and choose what to use dynamically. |
Happy Chinese new year! There is a scene. I build a SaaS service website (1.1.1.1) . User can let there own domain direct to my website. Beside, these changes are dynamic adding for my SaaS service.
Now I should make a TLS support to a.userowndomain.com (single domain) Can I make a |
I think you can use |
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:
Describe the solution you'd like
Support muti-domain TLS in one iris application.
Describe alternatives you've considered
Additional context
Nil
The text was updated successfully, but these errors were encountered: