Well what can I say, browser-caching sucks from a developers point of view. I worked with this problem a while ago and after several days of experimenting I came to the conclusion that the only way to guarantee that a client gets an uncached image is to trick the browser to store it under a different filename in its cache (done with the random sequence in its URL).
I'm not saying it's the only way to do it, but it's the only solution I came up with. Brgds Mathias -----Ursprungligt meddelande----- Fr�n: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]]F�r Kumar Sameer Skickat: den 20 mars 2002 12:10 Till: [EMAIL PROTECTED] �mne: Re: When does a servlet reloads/recalculates ? The first approach (setting header) as u had guesssed, didn't worked....(can u please tell the reason) But the second(http://localhost/servlet/ImageServlet;123456789) worked !!!! But is there any cleaner method to get the result ? ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
