Want to do an SSL proxy in the cluster, there are a lot of problems to solve, I am all grateful to your advice

The application itself should not consider the connection, so want to establish an SSL proxy cluster, need to use HTTPS application directly behind this agent.

However, this requires the agent to manage multiple certificates.

And the agent to manage multiple certificates, it is necessary to know the request is sent to which domain, and to know that the request is sent to which domain is to be obtained from the HTTP host, but at the time of HTTPS judgment HTTP itself is not recommended, because HTTPS before HTTP to accept the request, Simply said that HTTP is an intermediate link of https, so that the death cycle is limited.

apache2.2 later through the extended protocol SNI can get to the request domain name, if the client browser needs to support this extension protocol, tested at least now XP system using IE6 is not supported.

This is the limit of work to deadlock.

Have any suggestions please give us a lot of advice.