Thanks for the reply. This will indeed stop the pages from caching: Response.Cache.SetCacheability(HttpCacheability.NoCache);
That's not quite what I was looking for. I would like the pages to be cached as long as they are signed in but once they signout I would like to remove them from cache or cause them to have to be fetched from the server. Is this possible? Thanks! Brian -----Original Message----- From: Marsh, Drew [mailto:[EMAIL PROTECTED]] Sent: Monday, June 10, 2002 4:22 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] FormsAuthentication.Signout and browser back button Brian Weeres [mailto:[EMAIL PROTECTED]] wrote: > After a FormsAuthentication.SignOut a user can still use the > back button to view previous pages because they are in cache > and never hit the server for authentication. If they refresh > a page or cause a postback they go to the login page as > expected. Is their any way to remove pages from cache or > cause them to always refresh after a signout is done?=20 =20 > Thanks! Brian This is standard HTTP caching. If you don't want your ASP.NET pages cached client side you need to use the HttpResponse::Cache[1] property which returns an HttpCachePolicy[2] instance that you can use to choose how to expire your content. HTH, Drew [ .NET MVP | weblog: http://radio.weblogs.com/0104813/ ] [1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/h tml/ frlrfSystemWebHttpResponseClassCacheTopic.asp [2] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/h tml/ frlrfsystemwebhttpcachepolicyclasstopic.asp?frame=true You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
