Question

At this moment I cannot make changes to the code behind for a few weeks, but can change the .aspx file.

We have some internal users that will click the IE7 “back” button to navigate back 5 or 6 pages (which is specifically against stated rules and training). There are a very few pages where this is causing us major problems with duplicating transactions because the buttons that should be disabled, were enabled in past pages. I am trying the OutputCache directive which causes the user to see that the “page has expired”, but I anticipate that they will then click the “refresh” button, and then presents the same problem.

As I said this is a temporary fix until I can modify the code-behind in a few weeks.

Instead of getting the “page has expired”, can I have it go to a different .aspx using javascript? Basically, I’ll be sending them to the page at the level above, where they can then pick this page and enter it correctly.

Thanks.

Answer 1

http://plugins.jquery.com/project/history

It will take a bit of work in modifying your client side logic, but overall it should be worth it until you can fix things at a higher level.