01-10-2012, 10:28 PM
I have a page that is a serious problem when user's hit the BACK button and get to it because it causes a ping-pong affect of going back, and then loading the next page again (and again and again) each time the user hits back.
Is there any way to know if the page being displayed is not the last page in the history?
If I can see that it is not the last page then I can send the user to the correct page instead of just pushing them forward.
01-11-2012, 01:10 AM
Why not just set a cookie (with no expiration, so it will just be an in-memory session cookie) on the page with the BACK problem. So then when you do get to the page the BACK goes to, if the cookie is present you know to send them someplace different (after erasing the cookie, on the assumption they might cycle back through again, possibly).
01-11-2012, 07:34 PM
There are several paths that a user can use to get to that screen with the ping-pong issue so I would need to clear the cookie the first time it loads off the server. Let me play with that idea. It is a good suggestion if I can make it work.
01-11-2012, 07:48 PM
Cookies are a problem for people that are blocking cookies, though. The actual root of the problem is the page that redirects people without their consent and this is where you should start solving the problem. Isn’t there any other way to achieve what you want?
01-11-2012, 07:51 PM
No more Ping-Pong!
01-11-2012, 07:52 PM
Cookies are a problem for people that are blocking cookies, though. The actual root of the problem is the page that redirects people without their consent and this is where you should start solving the problem. Isnít there any other way to achieve what you want?
No, not in this case.
And all the users must have cookies enabled or they can't get this far into the application.