Asp.net System.Web.HttpContext.Current.Session null in global.asax
I have a custom security principal object which I set in the global.asax for the current thread and all is well, no problems normally.
I have a custom security principal object which I set in the global.asax for the current thread and all is well, no problems normally.
I’m having trouble getting 2 identical ASP.NET MVC applications to share the same Session using a Session StateServer. The reason I’m trying to do this is we will eventually be deploying this app across 3 web servers that need to share the same state. We need to use StateServer because we are trying to minimise use of the db for non data-related storage.
I have this really weird problem and I’m sure I’m missing something obvious here. I have these two lines:
I was told this works, but…
When a new async thread has been spawned using this signature, will the ASP.NET session object be available to the this new thread?
For a web application I switched from using ASP.NET Membership to using my own log in system which just does something like this to mark a user as logged in:
I have an asp.net site that I need to have a popup/layer/alert happen when the session reaches its timeout (lets say 10 minutes). The popup will say that your account session will exprire due to inactivity and have a button for continue session or a button for logout.
My application has a control of User Permissions, because not all users can access full website. At this moment, all those permissions for an specific user are stored in his session, ’cause It would be a problem for me to search at Database every Post Back.
Where exactly are session variables saved? Cookies? Server memory?
I have an issue with GenericHandler and anonymousIdentification.