Stuart Maclean, It will be nice if you can give me your code. I am also facing the same problems.I am having a form(jsp page) which will take data entered by user and then call other jsp page which will just display a gif file.Actualy we are generating a gif file and the text entered by previous page will be embeded in a gif file.This gif will be desplyed in a JSP page. The problem is when I am going back to the previous page and changing some data that changed data is not getting reflected in gif file.I am suspecting that my jsp page has been catched by the browser and that's why my page is not getting updated. Can you please suggest a solution for this. Prakash D. -----Original Message----- From: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Stuart Maclean Sent: Wednesday, September 13, 2000 1:16 AM To: [EMAIL PROTECTED] Subject: Re: Quick question/Off topic Sorry if this is slightly off topic and I know its been covered before but I've seen it done different ways, in jsp how are you guys making sure your dynamic pages get reloaded (! not cached by the browser) and are you using the meta tag or a response header. Any code snippets? thanks.. cause the way i'm doing it now doesnt work thanks rick I brought this up a while back. Your query is the opposite of mine, but I found a solution to the non-cacheability of JSP, in terms of not setting Last-Modified header. JSP doesn't support the servlet notion of 'getLastModified' call during the 'service' method. So I built a technique whereby you map the URL to a servlet, not a JSP, at say foo.jsp. The servlet does whatever if needs to do to ascertain the lastmodified time, maybe just get (and save!) current time. In doGet(), it uses the RequestDispatcher to include the 'wrapped' JSP page foo.wjsp. You have to map *.wjsp to the Jsp servlet, but thats easy. I think its a nice, general, technique. You can build a base JspWrapper servlet class which does the including, say from foo.jsp -> foo.wjsp, a simple string manipulation, and then subclass this class for specific scenarios of 'getLastModified'. I used this when a JSP page was built from data in a db which didn't change once formatted. Not only do you not go back to the db, you don't even send the HTML more than once (to a client which provides an If-Modified-Since header of course). I can provide code if anyone wants a further look... stu -- Stuart Maclean, Research Associate University of Washington ITS Research Program, College of Engineering Box 352500 Seattle, WA 98195-2500 Tel: (206) 543-0637 http://www.its.washington.edu ___________________________________________________________________________ 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 ========================= 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=P http://www.jguru.com/jguru/faq/faqpage.jsp?name=rvlets ___________________________________________________________________________ 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
