Strangely I can't find any documentation on this...
Does the browser cache XSL files? Does it just cache the resulting transformation? What about the url's within the xsl file pointing to other xml files? Does anyone have any links for details on this?
bogocles
07-14-2008, 02:16 PM
Off the top of my head, I've got no links on this specifically, although I don't think they would be too hard to find. Then again, on minor points like this, it can often take an entire day to locate someone else's resolution.
I do know that browsers act differently here, at least in their default behavior. Whenever testing in FF, it seems that changes I make to the XSLT sheet usually get applied upon a simple refresh. In IE, however, it seems that I had to actually clear the cache through internet options.
I'm pretty sure I was able to get around the problem of not having the browser do what I had intended simply by taking control of the response headers. I was using PHP, but any way you can set the Cache-control response header to your desired directive will work. By way of example, I would achieve this like so:
header ( 'Cache-control: no-store, no-cache' );
But check out this link:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
You'll have to scroll down about a fifth of the scroll bar to see the entry on Cache-control, but its all there. All browsers should obey the response headers as long as you can find a way to send them, however, we can all think of a single browser that is usually programmed to do its own thing. I take no responsibility for problems arising due to such rogue behavior. ;)