[prev in list] [next in list] [prev in thread] [next in thread] 

List:       struts-user
Subject:    AW: Caching problem
From:       "Lemke, Volker" <volker.lemke () infor ! de>
Date:       2000-09-26 8:48:13
[Download RAW message or body]

Hello all,

I've tried the meta-tag from veronique but for the MS-IE it seems that
they do not work. 
I use struts and have switched the action-servlet to no-cache, 
so request-headers for expires, no-cache etc. are generated.
If someone has another approach for that let me know..
 

Freundliche Grüße
Volker Lemke
Entwicklung Dorsten
Development department Dorsten


infor business solutions AG
Niederlassung Dorsten
Barbarastraße 70
46282 Dorsten
Tel.: 	+49 (0)2362/ 973-0
Fax: 	+49 (0)2362/ 973-111
Mobil 	+49 0170 3349 260

mailto:volker.lemke@infor.de
http://www.infor.de




-----Ursprüngliche Nachricht-----
Von: Veronique Dupierris [mailto:veronique.dupierris@INRIALPES.FR]
Gesendet: Freitag, 1. September 2000 13:41
An: JSP-INTEREST@JAVA.SUN.COM
Betreff: Re: Caching problem


This is exalctly what is happening... the page corresponding to your refresh
is
cached, so the vrowser will not send the request to the server again but
will get
the cached file. So, you have to set one or all of the following headers in
your
pages ! I think that you have to use more than one of these in order to
disable
page  caching in most browse (ie - nsc... )
From previous post :
<meta http-equiv="Expires" content="0">
<meta http-equiv="Last-Modified" content="0">
<meta http-equiv="Cache-Control" content="no-cache, must-revalidate">
<meta http-equiv="Pragma" content="no-cache">

"
I think you'll also want (need?) to include HTTP headers as well.
Specifically, you'll want to include an "Expires" header (for HTTP 1.0
browsers), a "Pragma: no-cache" header (particulary for Netscape 3), *and*,
finally, a "Cache-control: no-cache" header (for HTTP 1.1 browsers).
"
Hope this Helps
Regards
Veronique



Anjan Ghosh a écrit :

> Hi all,
> I have the following problem.
> I have two frames - leftframe and rightframe - in an HTML page. The
> leftframe shows a list of key fields. On clicking one item in the list,
the
> corresponding details is fetched from the database and shown in the
> rightframe. The user can edit the data in the rightframe and then submit
it.
> Now, the problem is, after the data is updated in the database, when the
> user again clickes on the same list item in the leftframe, still the old
> data is shown ( it is now not fetched from the database ). But when I
right
> click on the rightframe and click 'Refresh' from the menu, i get the
actual
> page with the current updated data.
> Can you tell me why this is happening and how do i solve this problem
>  which appears to me, as if, the browser is caching the previous pages and
> showing them in the second time also without going to the database and
> fetching the record).
> Please suggest what I should do to stop the browser cache the pages.
>
> Regards,
> Anjan
>
>
===========================================================================
> To unsubscribe: mailto listserv@java.sun.com 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

===========================================================================
To unsubscribe: mailto listserv@java.sun.com 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

[prev in list] [next in list] [prev in thread] [next in thread]