Try putting both of the following in the <HEAD> element of your page. Please let us know if it works.
<META NAME="Pragma" CONTENT="no-cache">
<META NAME="Cache-Control" CONTENT="no-cache">
From the HTTP1.1 spec:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32
14.32 Pragma
The Pragma general-header field is used to include implementation- specific directives that might apply to any recipient along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however, some systems MAY require that behavior be consistent with the directives.
Pragma = "Pragma" ":" 1#pragma-directive
pragma-directive = "no-cache" | extension-pragma
extension-pragma = token [ "=" ( token | quoted-string ) ]
When the no-cache directive is present in a request message, an application SHOULD forward the request toward the origin server even if it has a cached copy of what is being requested. This pragma directive has the same semantics as the no-cache cache-directive (see section 14.9) and is defined here for backward compatibility with HTTP/1.0. Clients SHOULD include both header fields when a no-cache request is sent to a server not known to be HTTP/1.1 compliant.
Pragma directives MUST be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives might be applicable to all recipients along the request/response chain. It is not possible to specify a pragma for a specific recipient; however, any pragma directive not relevant to a recipient SHOULD be ignored by that recipient.
HTTP/1.1 caches SHOULD treat "Pragma: no-cache" as if the client had sent "Cache-Control: no-cache". No new Pragma directives will be defined in HTTP.
Note: because the meaning of "Pragma: no-cache as a response
header field is not actually specified, it does not provide a
reliable replacement for "Cache-Control: no-cache" in a response
-----Original Message-----
From: Peter Alfors [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Can anyone help with solving the "BACK" button problem, in
th e browser?
Thane ,
I am using:
<META http-equiv="Expires" content="now">
in my header, and my action is not re-executed when I use the browser
back button.
Is there another option I should be using?
thanks,
Pete
Thane Eisener wrote:
>
>
> I seem to recall a META tag called something like pragma-no-cache that
> you can embed in your page which will force the page to reload (not
> just display a snapshot). This should enable handling the situation in
> scriptlets or your action class.
>
> -----Original Message-----
> From: Peter Alfors [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 9:52 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Can anyone help with solving the "BACK" button problem,
> in
> the browser?
>
> Depending on which browser you use, and the data on the page, the back
> button
> may cause (or ask) the page to reload.
> However, some browsers (like IE) only display a snapshot of what the
> last page
> rendered to.
> Therefore, you cannot use scriptlets or the action class. However,
> you are able
> to kick-off javascript.
> If you can gaurantee that your users will have javascript enabled, you
> can write
> a simple test to see if this page was already displayed to the user.
> You could
> check a flag (hidden field) when the page loads. If the flag is true,
> then use
> the javascript to reload to your desired page.
>
> HTH,
> Pete
>
> "Dudley Butt@i-Commerce" wrote:
>
> > Please help,
> >
> > When the user pushes the back button, I want the page to redirect or
> refresh
> > to a different page, please, any ideas?
> >
> > Thanx guys and gals
> > Dudley
