4 ms·
I thought SSL pages/resources aren't cached like they would be normally under regular HTTP, so there would still be extra latency (for repeat visits) if you eve
by plasma 15y ago
I thought SSL pages/resources aren't cached like they would be normally under regular HTTP, so there would still be extra latency (for repeat visits) if you ever visited a website that required SSL everywhere (like say Github).
Or is my assumption wrong here?
- briansmith 15y agoThis 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.
- JeffRodriguez 15y agoIt'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.
- TeHCrAzY 15y agoIts 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.
- TeHCrAzY 15y agoYou can see the direct result of that: lots of ajax'y functionality, and the reduction of full page refreshes.
- mike-cardwell 15y agohttps 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