Romain, Try setting the HTTP Header field Cache-Control to no-cache. I found the code below at http://www.zope.org/Members/rbeer/caching: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <dtml-call "RESPONSE.setHeader('Expires', '-1')"> <dtml-call "RESPONSE.setHeader('Cache-Control', 'no-cache')"> <dtml-call "RESPONSE.setHeader('Pragma', 'no-cache')"> <HTML> <HEAD><TITLE><!--#var title_or_id--></TITLE></HEAD> <BODY> --- Romain Slootmaekers <romain@zzict.com> wrote:
Yo, We have problems with some browsers being to eager to cache images, and therefore not displaying the right image when the image has changed at server side.
This is especially so with Netscape 4.7X. Setting the browser's cache preferences to 'compare every time' doesn't help much.
This problem is especially annoying after an image upload: the user changes the file with an upload but the image displayed by the browser remains the same.... and thus the user gets confused.
Anyone any ideas ?
TIA,
Sloot.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
__________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1