I think that browsers are more aggressive caching images than html. The assumption seems to be that images do not change as often. That's not authoritative, just my theory from experience trying to do things like what you're doing. The good news is that browsers should respect a last-modified http header, and/or an expires header set in the past. Probably the second is more important. What I don't know is if cocoon has currently working functionality to set those headers. I remember a past discussion where I thought this was in the process of being fixed.
Geoff Howard > -----Original Message----- > From: Spectron International, Inc. [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 25, 2002 3:10 PM > To: Cocoon Users Mailing List > Subject: No-caching for SVG's > > > I asked this before but I didn't got a definite answer so > I'll ask this > another way. I'm creating SVGs using information retrieved > from a database > that can change at any time. I don't want the SVG's cached > anywhere. Right > now when I click on a link that will display an SVG it works, > but if I click > 'Back' and then click on the same link again it changes the > page contents > but not the SVG, I have to click on 'Refresh' to update the > graph. Is there > a way to refresh the SVG as well? > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
