June, even. I'm still interested, though. Fitbit uses haproxy but I set up my development machine with nginx because of SSL. It probably doesn't make a difference, but I'll still feel better when I can easily make my dev setup more closely mirror production.
From what I recall, the SSL functionality was in haproxy for a while now. Some time ago, when I was doing research if I have other options for SSL enabled LB other than Nginx, I found the information that haproxy has such support included, but for some reason I decided to go with Nginx anyway.
I didn't investigate deeply; I'd never heard of haproxy prior to Fitbit. Someone from site ops told me they use nginx + haproxy but it would be easier for me to just set up nginx.
SSL support has been around for a while, but 1.5 has been considered beta for a few years now, though that hasn't stopped it from being deployed in a lot of production environments.
Before SSL was rolled into haproxy, nginx was often a good candidate to handle the SSL termination. Stunnel is also common, and stud was popular for a while, but seems it was abandoned once haproxy could handle the job.
