Re:Yes, browsers do cache SSL resources, so please use Googl...
by sdizdar on Wednesday January 19, 2011 @02:37PM
(#2120940)
Question: The article says that if a resource is accessed as 'http:' and then as 'https:', then the second access will not hit the cache. Is that true? Thanks.
[ Parent
| on HN ]
Re:Yes, browsers do cache SSL resources, so please use Googl...
by briansmith on Wednesday January 19, 2011 @02:42PM
(#2120960)
They are different resources so they are cached separately. There is no standard that says that a cached response for https://foo.org/x can be used for a request to http://foo.org/x.
Re:Yes, browsers do cache SSL resources, so please use Googl...
by davidu on Wednesday January 19, 2011 @04:50PM
(#2121409)
Those would be different URIs, and thus different URLs, and thus have different caching policies. URIs (and in turn URLs) must be consistent for caching to apply.
Consider:
https://foo/a.txt != http://foo/a.txt
just like the obvious case of https://foo/b.txt != http://bar/c.txt
All of those are considered unique URIs.