Weeell, there is 3 possible solutions for https.
The first one - current solution except of common cert for all of the backend, from my point of view - the most proper solution. Haproxy don't know anything about ssl and just do balancing on tcp level.
![image](https://f.cloud.github.com/assets/3116070/787442/15bb7772-eada-11e2-85a8-6f8a827cac69.png)
The second one - when balancer owe ssl cert and provide https to end-user, we don't care about ssl between haproxy and backend and able drop support ssl on each of services. The solution makes no sense cause both traffics - secured and unsecured, flowing on same network.
![image](https://f.cloud.github.com/assets/3116070/787491/53916934-eadb-11e2-89d8-39320682e8f0.png)
The third one - when haproxy owe cert to provide ssl for end-user and establishing https connection to backend. This solution will work, but there is a lot of overhead for ssl on haproxy and a lot of manual work during deployment to put individual certs on each of the backends and haproxy.
![image](https://f.cloud.github.com/assets/3116070/787520/03b78406-eadc-11e2-9c44-4ce9572b53e7.png)
Wich of those solutions you propose should be emplemented and supported by loadbalancer?