I have an asp.NET application which has a fairly heavy mainpage. The content of this mainpage is only rarely changed, except by actions on that same page.
How do I make the browser retrieve the page from cache when the user presses the "Back" button in the browser, instead of contacting the server every single time, forcing it to render the page again?
Thanks, Jonas
The short answer is: You can't.
I think the closest you can do is to include some HTML Meta tags in your webpage, specifically the one relating to caching and expiration such as:
<META HTTP-EQUIV="EXPIRES" CONTENT=" [some date/time in the future] ">
and
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="PUBLIC">
Once you've included these in your rendered web page that is sent to the client browser, you just have to hope that the browser, upon the user clicking the back button, will displayed a "cached" version of your page rather than instigating another request/response cycle to your web server, thereby causing your web page to be re-requested and re-rendered. You will have no control over this, though, and it's entirely down to how the browser wants to handle it. I believe most modern browsers will re-request the page, though.
Another approach to preventing re-rendering of an ASP.NET page is to control this yourself on the server-side using the
directive within your ASP.NET web page, like this:
<%@ OutputCache Duration="600" VaryByParam="None" %>
At it's most basic, the @OutputCache control will cache your rendered ASP.NET page for a specified number of seconds (600 in the example above) so that subsequent requests for that page will result in the ASP.NET runtime serving up the already rendered version of the page to the user, rather than re-processing and re-rendering the entire page. Be aware that this is not user-specific, though.
More info on page output caching (which is probably the closest you'll get to what you're after):