This is exactly the behavior that the HTTP spec requires.  In fact, most browsers are slightly broken, in that the spec actually says that history and cache are different and should be kept seperately.  However, either way, the back button should not refresh the page by definition.
 
You might be able to accomplish this using Javascript, however (document.body=????). Depending on how much you care whether you annoy your users, you could also place a <META HTTP-EQUIV="refresh" CONTENT="10; url=blah.com/page"> to force a refresh of the page every 10 seconds.  I think that this will function even on a page back (I could be wrong about that, as I find it very annoying and would never do it).
 
J
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]]On Behalf Of David Wall
Sent: Tuesday, December 28, 1999 11:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Refresh Pages when clicking on the forward or back buttons

It seems safe to say that the browsers just won't honor these when it comes to using the BACK/PREV button.  They always seem to grab from cache.
 
David
----- Original Message -----
From: Yang Lu
Sent: Tuesday, December 28, 1999 8:35 AM
Subject: Refresh Pages when clicking on the forward or back buttons

Is there a way to force the browser to reload the whole page when clicking on the forward or back buttons?
 
We've tried all of the following:
 
                <META HTTP-EQUIV="Expires" CONTENT="10/01/1999 00:00:00 GMT">
                <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
                <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">
                <META HTTP-EQUIV="content-type" CONTENT="text/html">
 
Any suggestions?
 
Thanks.

Reply via email to