You can also script it. like the following:
response.setDateHeader ("Expires", 0);
response.setHeader ("Pragma", "no-cahce");
if (request.getProtocol ().equals ("HTTP/1.1")) {
response.setHeader ("Cache-Control", "no-cache");
}
this piece of code is in Kolb and Fields' book "Web Development with
JavaServer Pages"
page 92 (ISBN 1-884777-99-6)
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
> Hoolehan
> Sent: Wednesday, June 20, 2001 4:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] cache
>
>
> That's a browser issue. If you're on IE or Netscape, you can change the
> settings to always compare documents to cached versions. This should fix
> the problem. Also, if you're on Netscape, you can just hold down
> shift and
> click the reload button. This will force a non-cached reload.
> Mike
>
> On (20/06/01 12:14), Richard Bottoms wrote:
> > Okay, I got hello working. Now, I made a minor change to the
> servlet code,
> > going to black bgcolor in the body tag. After deployment the old cached
> > version is displayed in the browser.
> >
> > Is there any way to force clearing a cached servlet response?
> >
> >
> > thanks,
> > r.b.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
