- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 14 Feb 2010 12:47:33 +0100
- To: Jonas Sicking <jonas@sicking.cc>
- CC: public-html@w3.org
Jonas Sicking wrote: > On Sun, Feb 14, 2010 at 3:27 AM, Julian Reschke <julian.reschke@gmx.de> wrote: >> Jonas Sicking wrote: >>> Out of curiosity, for a document like: >>> >>> <!DOCTYPE html> >>> <html> >>> <head><title>...</title></head> >>> <body> >>> <img src="myPic.jpg"> >>> <img src="myPic.jpg"> >>> </body> >>> </html> >>> >>> and with a GET request to myPic.jpg returning cache-control:no-cache >>> >>> Should this result in two requests being made to myPic.jpg? If not, is >> No. >> >>> that considered ignoring HTTP caching rules? >> It depends on what HTML says about how the <img> tag is processed. > > How does it depend on what HTML says? > > I.e. under what conditions would HTML requiring your "No" answer above > be violating the HTTP caching rules? And under what conditions would > requiring your "No" answer not violate the HTTP caching rules? > > Or am I misunderstanding your answer? It depends on whether the language requires the two tags to be treated one-by-one. For instance, in XSLT it is clearly stated that the result of fetching something using XPath's document() function can be re-used throughout the stylesheet execution. Essentially,
Received on Sunday, 14 February 2010 11:48:13 UTC