4 ms·
This is some pretty sweet news. This was one of the reasons why I ended up not using AWS ELBs. I wonder if this will make an impact on Heroku's pricing for SSL.
by wmwong 16y ago
This is some pretty sweet news. This was one of the reasons why I ended up not using AWS ELBs. I wonder if this will make an impact on Heroku's pricing for SSL. I assume they had to somehow get around the technical difficulties themselves.
- dasil003 16y agoI wonder if this was one of the reasons Engine Yard doesn't use ELBs? Instead they use ha-proxy, which unfortunately can not terminate SSL, and due to unchangeable kernel settings on EC2 can not pass a direct TCP connection through. The result: you can't see client IPs on SSL requests on EY AppCloud! We got burned pretty bad by this due to the fact that we are a global VOD site that depends on geo location for film availability. It wasn't terribly difficult to workaround, but it's not the kind of thing you'd expect as a web developer. I would LOVE to get on an ELB, assuming that failover can be handled gracefully.