page has expired warning

[jwhite68]

I have seen several posts on this subject on the net, but no clear solution.

 

I have a php page that presents a summary of 'objects', after which the user selects an object to see the 'detail' page of an object.  On this detail page there is a 'back to previous' hyperlink, which simply goes back 1 page in the history.

 

However, in this case, it always comes up with the Warning: page has expired first.

 

Since what I am trying to do is very standard and normal in PHP - is there anyway at all (without resorting to GET) to prevent this annoying behaviour?

[chrisuk]

i thought I had an idea for you....until you said you'd rather avoid get

 

in a system I made there was a simple search and in order to go back i provided a button which resubmitted the original search string sotred in a variable via GET and that way essentially performed the search again.

 

Inefficient but it worked and it's alot neater than the expiry warnings

[jwhite68]

Yes, I have been trying a variation on that theme, using session variables instead - but still havent worked out the logic yet for clearing the session variables down.

 

I was storing the actual SQL query in a session variable, to resubmit in the relevant PHP script.

 

Principally it works. But since someone can submit another search query, the value of this session variable is still set, so it continues to use it everytime.

[per1os]

Well post the code and we can help with the logic.

 

POST data always does a "postback" which is why you see that error. No matter what if you send POST data to the page and a back button is pushed that will be the error you get.

 

There are a few ways to work around it, 1 simply use AJAX. Use ajax to submit the search query behind the scenes and either store the data in session and redirect the page or just return the data and parse it on the page itself.

 

The other way is you POST the data with the submit to the processing page, in the processing it querys and than stores it in session and redirects you to the "display" page, this will clear the post data from cache and the back button should take them back to the initial page.

[jwhite68]

Thanks, but I managed to sort it out.  Basically, I did use session variables - and instead of storing the SQL query - on the page I may want to come back to, I store the $_REQUEST parameters in a session variable, together with the full URL.  Then on my back to previous link, I use the value of this session variable.  Appears to be working well.

[cooldude832]

what if when it goes back the page is refreshed? if refreshing the page works try setting up a HTTP_REFERAL system where it it refers from the next page it auto refreshes the page once to get it clean