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
When connecting to the backend https server, sometimes the backend server may need the Server Name Indication (SNI) to choose the proper certificate.
In nginx, it needs proxy_ssl_name and proxy_ssl_server_name on; configurations (see http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ssl_name and http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ssl_server_name). We may probably want to specify those configs optionally on https connection.
proxy_ssl_name
proxy_ssl_server_name on;
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When connecting to the backend https server, sometimes the backend server may need the Server Name Indication (SNI) to choose the proper certificate.
In nginx, it needs
proxy_ssl_nameandproxy_ssl_server_name on;configurations (see http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ssl_name and http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ssl_server_name). We may probably want to specify those configs optionally on https connection.The text was updated successfully, but these errors were encountered: