We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SNI is the only way to support multiple certificates for TLS using multiple domains over the same Ip address.
SNI allows loading of specific Certs using a server name param during the TLS handshake.
See: https://medium.com/@satrobit/how-to-build-https-servers-with-certificate-lazy-loading-in-go-bff5e9ef2f1f
The text was updated successfully, but these errors were encountered:
simonmittag
No branches or pull requests
Why
SNI is the only way to support multiple certificates for TLS using multiple domains over the same Ip address.
SNI allows loading of specific Certs using a server name param during the TLS handshake.
See: https://medium.com/@satrobit/how-to-build-https-servers-with-certificate-lazy-loading-in-go-bff5e9ef2f1f
The text was updated successfully, but these errors were encountered: