G
Guest
Hi,
I have an application where I need to ensure that users do not use browser
navigation buttons. I specifically warn the users, and in every page set the
folllowing:
Me.Response.Cache.SetNoStore()
Me.Response.Cache.SetNoServerCaching()
Me.Response.Cache.SetCacheability(System.Web.HttpCacheability.NoCache)
and issue a GUID for every page. Then on page load I check whether the GUID
passed from the last page is the same as in Session, and display an error
message othewise. All works - in development.
However, in production (the site is deployed to a web hosting company),
using navigation buttons in IE do not force re-load from the server, and
therefore do not trigger the error. It works without any hiccups with
Netscape & Mozilla, both in development and production.
Any help on how to force IE to re-load the page, or why
Response.Cache.SetNoStore() stores page in IE history is greatly appreciated.
I have an application where I need to ensure that users do not use browser
navigation buttons. I specifically warn the users, and in every page set the
folllowing:
Me.Response.Cache.SetNoStore()
Me.Response.Cache.SetNoServerCaching()
Me.Response.Cache.SetCacheability(System.Web.HttpCacheability.NoCache)
and issue a GUID for every page. Then on page load I check whether the GUID
passed from the last page is the same as in Session, and display an error
message othewise. All works - in development.
However, in production (the site is deployed to a web hosting company),
using navigation buttons in IE do not force re-load from the server, and
therefore do not trigger the error. It works without any hiccups with
Netscape & Mozilla, both in development and production.
Any help on how to force IE to re-load the page, or why
Response.Cache.SetNoStore() stores page in IE history is greatly appreciated.