Hi All!
I have a webpage where union members can lookup various information about their membership.
In the page load event of all pages I have the following code. If the session expires I set a session flag then test it in GlobalProcs.TestLogin(). If its true I redirect the user to the login page.
Response.Cache.SetCacheabi
Response.Cache.SetExpires(
GlobalProcs.TestLogin()
When the user login the are directed to a sumamry page. Then they can go to a dependents page. In a dependent page I have a dropdpwn where they can choose a dependent. When they choose one the data on the page is refreshed.
I have 2 issues
Can I somehow use FormsAuthentication to see if a user is logged in without using a session variable. I am worried that setting a session variable resets the session. Maybe this is not a big deal since I clear out the session anyway.
When the user changes the dependent, click the back button and then the forward button I get an error that the webpage has expired. It seems like I cannot navigate to a page that resulted from a postback when I have NoCache set. Is there any way to fix this.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ThogekPosted on 2008-03-17 at 11:16:31ID: 21144676
For #1...
It might be good to make sure that you're familiar with the various classes related to ASP.NET membership, some of which give give various ways to access the current logged-in user's info (and, thus whether there is a current logged-in user). See http://msdn2.microsoft.com
For #2...
I think what you're running into is the simple fact that most browsers simply do not cache pages that were the result of POST requests. These include ASP.NET PostBacks, so, yes, if you Back from and then Forward back onto a PostBack'd page, the browser's going to tell you that it no longer has that page in cache, and you'll have to submit to the server to get it. I'm not aware of any way to tell the browser to do otherwise -- it's actually in part related to a limitation in the way browser's index their cached pages.