You have pages in your application you want to cache but ASP.NET does not provide built-in support for the dependencies you need, such as browser type and full version number.
Add the @ OutputCache directive at the top of the .aspx file of each page you want to cache. Set the VaryByCustom attribute to the name of a custom string, such as "BrowserFullVersion":
<%@ Page Language="VB" MasterPageFile="~/ASPNetCookbookVB.master" AutoEventWireup="false" CodeFile="CH16CacheByCustomStringVB.aspx.vb" Inherits="ASPNetCookbook.VBExamples.CH16CacheByCustomStringVB" Title="Cache By Custom String" %> <%@ OutputCache Duration="10" VaryByParam="none" VaryByCustom="BrowserFullVersion" %> …
Override the GetVaryByCustomString method in global.asax and write code that builds a unique string for the value you have assigned to the VaryByCustom attribute. Examples 16-1 and 16-2 show VB and C# GetVaryByCustomString method to return a full browser version number.
ASP.NET provides the ability to control the caching of pages as a function of custom strings that you provide, which gives you the ability to control the caching by variations not directly supported by ASP.NET. In the example we use to illustrate this solution, we show how to cache pages based on the browser type, its major version number (integer portion of version number), and its minor version number (the decimal portion of the version number).
The first step in this recipe is to add the @ OutputCache directive shown earlier to the .aspx file of the page you plan to cache. Set the VaryByCustom attribute to the name of the string that is to be used to determine caching. In our example, we have named the string "BrowserFullVersion".
Next, you need to override the GetVaryByCustomString method in global.asax to return the full browser version when the passed parameter (arg) is set to "BrowserFullVersion". This provides a unique string for each browser and version to allow ASP.NET to differentiate between the browsers and use the cached version of the page accordingly.
This technique is not limited to caching by browser version. You can use almost any information to identify pages that should be cached separately. For example, you could use a value stored in a cookie to determine the uniqueness of a page. The cookie collection is accessed through the Request object in the same manner as the Browser data (context.Request.Cookies).
One thing you cannot use is Session information. The reason for this is that when GetVaryByCustomString is called, session information has not been retrieved from session storage. The session ID is available but not the session data. If you need to use a value related to a specific session, the data will have to be stored in a cookie first and used as described previously.
Search for "Caching Versions of a Page, Based on Custom Strings" in the MSDN library.
Example 16-1. GetVaryByCustomString method in global.asax (.vb)
Example 16-2. GetVaryByCustomString method in global.asax (.cs)