IE8 back button stops running on ASP.NET page

Question

If you search to disable the "ie8 back" button, you will see a series of blogs with people who have difficulty with the Internet Explorer version 8 button disabled. This happened on one of my ASP.Net pages. The page uses a user control, an aspx page, and the main page. It doesn’t use redirects and seems to happen when I press the back button and then the forward button (after clicking the forward button it does not fire the Download event, and the back button is disabled). Has anyone else come across this and do you have a solution for this?

Answer 1

It does not use redirects

Maybe you should try a few. It is best to redirect after any postback that causes a “transaction” (the definition of a transaction is in the eye of the observer). One of the benefits of this is that it’s much easier for the browser to find out where you are, like the back and forward buttons.

Answer 2

This is most likely the result of cache and history directives in the http headers. Pay particular attention to the no-cache and no-store headers and read about their effects (and non-effects) in different browsers. I would like to point you to the final source on this issue, but reliable information about these headings is seriously missing on the Internet. Many will point you to the latest HTTP RFC requests, but unfortunately, browser vendors, as usual, have their own unique RFC connections.

Answer 3

We had the exact same problem .

The bottom line, the problematic page is aa gigantic, bloated viewstate , which for some reason made IE “forget” the page whenever the user clicked “back” and then “translated”.

We tried to execute this answer (i.e. use the no-cache and no-store headers), but that didn't work.

What the job did was simply reduce the amount of data sent to the page.
Not a perfect solution, but it's better than nothing.