Hi Moondaddy,
From your description, you found when you use "forward and back" button on
the client browser to view a requested page, you 'll get "Page has
Expired" error,yes?
Generally the "Page has Expired" error is caused by the page's client side
cache has been expired. In most cases, we need to write code to manually
make it expire , however your problem seems that you don't want it expire
but it does. So I think you can check the following things first:
1. Try viewing the page from different client machine to see whether it can
repro on different machine. Thus, we can confirm whether its due to
clientside browser or the server side's setting.
2. Is the problem only focus on a certain page, if so , would you have a
check on the page's code to see whether it has any code to set the
clientside cache. You can view the following referen in MSDN on this:
#Setting the Cacheability of a Page
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconsettingcacheabilit
yofpage.asp?frame=true
Especially notice the below description in it:
======================================
Note If you set cacheability to HttpCacheability.NoCache or
HttpCacheability.ServerAndNoCache, the requesting client will not cache
pages in its History folder. For example, any time a user clicks a back or
forward button, a new version of the response will be requested. You can
override this behavior by setting the
HttpCachePolicy.SetAllowResponseInBrowserHistory method to true.
==================================================
If you still not sure, please provide the page's complete code or it's
better if you can generate a simple demo page to repro the problem. Thus
I'll try testing on myside to do some furthure researh.
Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx