问题原文
原帖链接 · Tempestas Ludi · CC BY-SA 4.0
The TLS handshake initiation contains the requested domain in cleartext, to allow a server to select the correct certificate. Therefore, the server should be able to proxy the handshake, and all subsequent packets, to the correct domain/machine/server, without performing the authentication. Therefore, it should not need any certificates to perform this proxying. This would come in handy when there are a couple of servers in the local network, each serving one domain.
My question is: is it possible to configure apache(2) to proxy incoming requests, over a HTTPS connection to the correct domains, without it having access to the certificates for said domains?
已采纳解答
原帖链接 · Steffen Ullrich · CC BY-SA 4.0
Apache can only do proxying at the HTTP level which isn't sufficient for what you want to do. What you want instead is proxying at the TCP level based on the name in the TLS handshake (SNI) - nginx and haproxy can do this, Apache not.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
