page has expired Message

Hi All,   Has anyone found a solution concerning the message (warning: page has expired), when one clicks the back button or go(-1). I've tried the following with no success.: <cfcache action="CLIENTCACHE" timeout = "#DateAdd("h", "-1", Now() )#"> or <CFHEADER NAME="Expires" Value="Sun, 06 Nov 1994 08:49:37 GMT"> <CFHEADER NAME="Cache-Control" VALUE="max-age=7200"> TIA, Patrick Whittingham United Space Alliance   _____  

Whittingham, P wrote: >   >   Has anyone found a solution concerning the message (warning: page has expired), when one clicks the back button or go(-1). Was the page originally sent as the result of a GET or a POST request? Jochem

Try passing the values back to the same page, and provide a message asking the user not to use the browser back button, but use the button provided as shown below: <form action="[some page]" method="post"> <cfoutput> <cfloop collection="#form#" item="fieldName">   <input type="hidden" name="#fieldName#" value="#form[fieldName]#"> </cfloop> </cfoutput> <input type="Submit"   name="goback"   value="Go Back"> </form> > > Has anyone found a solution concerning the message (warning: page has > expired), when one clicks the back button or go(-1). I've tried the > following with > no success.:

You will always get this message if you are moving back to page which in itself was a form post (as the data to form this page does not techincally exists in the back request). There is no solution as far as I know....its by design.    _____ Sent: 26 May 2004 12:01 To: CF-Talk Subject: page has expired Message Hi All,   Has anyone found a solution concerning the message (warning: page has expired), when one clicks the back button or go(-1). I've tried the following with no success.: <cfcache action="CLIENTCACHE" timeout = "#DateAdd("h", "-1", Now() )#"> or <CFHEADER NAME="Expires" Value="Sun, 06 Nov 1994 08:49:37 GMT"> <CFHEADER NAME="Cache-Control" VALUE="max-age=7200"> TIA, Patrick Whittingham United Space Alliance   _____    _____  

post method. some of the form data is sensitive or more that 4k in length (lots of form elements). I been trying all the different method via google..... Pat Whittingham, P wrote: >   >   Has anyone found a solution concerning the message (warning: page has expired), when one clicks the back button or go(-1). Was the page originally sent as the result of a GET or a POST request? Jochem   _____  

Whittingham, P wrote: > post method. Responses to POST requests are only cacheable in special circumstances. The recommended workaround is not to send the response directly, but forward the user to another page that can be cached. See the HTTP 303 statuscode in RFC 2616. Jochem

i am using w2k servers,ie 6 and http1.1... Whittingham, P wrote: > post method. Responses to POST requests are only cacheable in special circumstances. The recommended workaround is not to send the response directly, but forward the user to another page that can be cached. See the HTTP 303 statuscode in RFC 2616. Jochem   _____