Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Pages only viewed once?
- Thread starter youradds
- Start date
Nope, back is cached in the browser.
There are two ways, prevent it with javascript, or:
put in the page u dont want to be cached <meta http-equiv="pragma" content="no-cache"> en the rest, must revalidate etc.
In this way the page must be loaded from the server.
the in that page check the referrer, if it is the last page mentioned, put the error message on the screen and die.
For exact meta statements you have to consult another resource, dont have any at hand.
Good luck mcvdmvs
"It never hurts to help" -- Eek the Cat
There are two ways, prevent it with javascript, or:
put in the page u dont want to be cached <meta http-equiv="pragma" content="no-cache"> en the rest, must revalidate etc.
In this way the page must be loaded from the server.
the in that page check the referrer, if it is the last page mentioned, put the error message on the screen and die.
For exact meta statements you have to consult another resource, dont have any at hand.
Good luck mcvdmvs
"It never hurts to help" -- Eek the Cat
gerrygerry
Technical User
use sessions.
check for a session variable when the page is loaded.. if it shows that the user has been there, echo a "you cant do that", otherwise, set the session var and display the page as planned. when the user tries to come back to the page (assuming you use all the no-cache headers you can), it'll detect the session var and give them a "you cant do that" error.
this is the best way to do it, short of storing each of the user's actions... this gets messy though. sessions are so easy! -gerrygerry
Go To
check for a session variable when the page is loaded.. if it shows that the user has been there, echo a "you cant do that", otherwise, set the session var and display the page as planned. when the user tries to come back to the page (assuming you use all the no-cache headers you can), it'll detect the session var and give them a "you cant do that" error.
this is the best way to do it, short of storing each of the user's actions... this gets messy though. sessions are so easy! -gerrygerry
Go To
- Thread starter
- #4
- Status