We have an ASP.Net (Web Forms) site hosted on IIS7.
The site contains a table with information retrieved from a database. Paging is enabled for this table, meaning that only 10 rows are displayed at a time. (This is done with server-side code; as far as the browser is concerned, the table contains no more than 10 rows.)
Once the DB reached over 1000 rows, the browser began disabling the back-button after the page loaded. Sometimes the back-button remained enabled until users navigated to another website, and only then became disabled (instantly).
After deleting some info in the DB, the problem stopped. But once the amount of records passed 1000, it started again.
This only happens with Internet Explorer (no matter what version). This does not happen with Firefox or other browsers.
Note: The back-button becomes disabled, but the history is all saved.
Why does this happen, and how can it be fixed?
The amount of records retrieved should only affect the server; the browser has no idea how many rows were retrieved. And yet, the "choice" to disable the back-button is client-side!
Here's a link to the question on StackOverflow.