Re:Improving HTTPS Performance with Early SSL Termination
by tagx on Tuesday August 14, 2012 @03:57PM
(#4382796)
Normal CDNs don't do this with dynamic content that changes on every user request. Each api request we serve is different and saving 200ms almost doubles the performance.
[ Parent
| on HN ]
Re:Improving HTTPS Performance with Early SSL Termination
by saurik on Tuesday August 14, 2012 @04:34PM
(#4382929)
This is at least incorrect for Akamai and CDNetworks (examples of large CDNs; if you are talking about something silly like CloudFlare, then all bets are off). I run my entire website, most of the content of which is dynamic, through CDNetworks; they definitely maintain hot connections from their systems through to my server, and use it for uncached origin fetches. For more information on related performance improvements, see one of my earlier comments.
Re:Improving HTTPS Performance with Early SSL Termination
by jaylevitt on Tuesday August 14, 2012 @05:51PM
(#4383237)
Sure, but Akamai is the "big iron" of CDNs - you can run your own custom code in a JVM at their edge locations. So I kinda think anyone in the market for Akamai isn't getting SSL termination advice on HN :)