A trick someone told me in IRC, although not the greatest thing, is to have
each page assign a random ID to the page. This "forces" the browser to get
the page from the server, even if caching is allowed. One benefit is that
images and stuff stay cached, but the pages get reloaded from the server. I
don't know if this works..but this person said it does.
We have caching problems too, especially with Netscape. Turns out if you use
the POST method to send a request to a servlet, the next page can NOT be
printed because Netscape doesn't display the source to pages returned via
the POST method. We have problems with that because we need to allow our
customers to print those pages.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
