That is generally true, however there is a meta tag (in HTML) for caching that can tell the browser (or intermediary servers - like the ISP) whether or not it is allowed to cache the current page. I don't know which versions of the various browsers support it, but most of the recent ones do.
Jefficus ----- Original Message ----- From: "Nelson, Laird" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 10:52 AM Subject: RE: [Q] Return-to-page - is there a slick solution? > > -----Original Message----- > > From: Jeff Smith [mailto:[EMAIL PROTECTED] > > While you're at it, you might want to ensure that getting > > back to the "start > > point" includes a nice, juicy screen refresh so that any > > dynamic information > > altered by your wizard sequence is updated on the page. :-) > > Yep; hadn't gotten that far yet. Incidentally, is it just me, or are these > types of return-to-a-page caching/non-caching issues utterly browser > dependent? I have vague recollections from the last time I burbled up to > the front end (I'm usually down in the server-side muck) that you could > never tell whether a browser was going to cache something or not. > > Cheers, > Laird > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
