2 ms·
You can have good cacheability—you just need to send explicit Cache-Control headers (which is a good idea anyway). If you don't do SSL properly (e.g. non-SSL-t
by pornel 14y ago
You can have good cacheability—you just need to send explicit Cache-Control headers (which is a good idea anyway).
If you don't do SSL properly (e.g. non-SSL-terminating load-balancer can break SSL session resuming by forwarding requests to different servers which don't share tickets) then you'll have lower front-end performance.
webpagetest.org nicely shows connections including time spent on SSL negotiation, so you can use it to check your SSL overhead.