Forms authentication timeout vs sessionState timeout
I have code that i am looking through regarding session time outs of the website. In the web.config i came across this code.
I have code that i am looking through regarding session time outs of the website. In the web.config i came across this code.
What is the difference between destroying a session and removing its values? Can you please provide an example demonstrating this?
I know what user is logged in with the following line of code:
I have an application where, in the course of using the application, a user might click from
What is the difference between storing a datatable in Session vs Cache? What are the advantages and disadvantages?
We have several ASP.NET applications deployed to a few servers. Is there a standard way to reuse session data or some other method to not require users to log in to the next application when moving from application to application if they’ve already authenticated? I’m hoping there’s a best practices way of doing this that you guys know about. I feel like there should be something easy that I’m missing.
As far as I know, the current situation is this: Use SQL session state provider is possible (as I’ve read somewhere) but it’s not supported by Microsoft. So it could stop working in the future. Also it needs a WorkerRole to delete the outdated data. Azure AppFabric Caching Service is still in CTP. TableStorageSessionProvider is … Read more
I’m wondering how to prevent Session fixation attacks in ASP.NET (see http://en.wikipedia.org/wiki/Session_fixation)
How can I list (and iterate through) all current ASP.NET sessions?