- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 20 Sep 2010 08:05:41 +0200
On 19.09.2010 22:33, Robert O'Callahan wrote: > ... > So for example, page A links to resource B. The browser does a GET on A, > and receives a document containing a <link> to B, and the <link> element > has etags or last-modified attributes. The browser has a cached resource > for B, whose etags/last-modified matches the <link> attribute, so the > browser knows its cached B is valid and no further network transactions > are required. > > The linked resource B "having the right caching information in the first > place" (when the browser first fetched it) isn't enough to eliminate the > need for an HTTP transaction to validate B later. > ... Well, it would if the caching information specifies an expiry time sufficiently in the future. Best regards, Julian
Received on Sunday, 19 September 2010 23:05:41 UTC