Re:False Start: Google proposal reduces SSL handshake to sin...
by briansmith on Thursday May 19, 2011 @11:27PM
(#2566265)
This used to be true, but it isn't true any more on modern web browsers. In particular, Firefox improved its caching policies for HTTPS in version 4.
Re:False Start: Google proposal reduces SSL handshake to sin...
by mike-cardwell on Friday May 20, 2011 @08:00AM
(#2567286)
https content is generally only cached in memory by the browser.
But if the response contains a Cache-Control header that explicitly specifies that the content is public, it can be cached to disk, just like http content. Eg:
Cache-Control: public, max-age=86400
Re:False Start: Google proposal reduces SSL handshake to sin...
by JeffRodriguez on Thursday May 19, 2011 @08:09PM
(#2565871)
It's a browser configuration thing, but I think you're right about the default.
Maybe a more intelligent approach would be to use "don't cache" if the server doesn't specify any caching headers. Otherwise, follow the server's recommendation.
Re:False Start: Google proposal reduces SSL handshake to sin...
by TeHCrAzY on Thursday May 19, 2011 @08:16PM
(#2565890)
Its not something that could be changed from the current "default" without high risk of big impact.
There would be need to introduce a new header to trigger SSL based caching, and migrate towards simply not sending the old/normal cache header.
Or is my assumption wrong here?