My web client requires client-side output caching because it uses its back and forward button Basically just calls the browser back / forward button).
However, the problem I am facing, however, (whenever the user exits from the app) the client-side output cache remains so that anyone can click on the "back" button and it seems I have discovered some solutions, but most of them do not include server-side output caching or any output caching.
I have had success with server caching and HTPRPS option. RemoveOutputCacheItem, but unfortunately caching I need client side
Is it possible to clear this client side output cache after logging out?
Is there any reason you want to explicitly delete the cache?
The best way to check user login is to add a config in the existing directory, for example: /section1/web.config
The main web In the config, you can set the redirect page if the user is not valid.
Log in users with the system.websecovery membership. When log out is pushed out, you can either use the member log-in timelines or you can explicitly log in using them:
FormsAuthentication.SignOut (); In this way you ensure security and keep the page cache.
Comments
Post a Comment