session-state

问题 How could I add some items to the tempdb anytime SQL Server starts up? I'm no expert at this, but our ASP SessionState is stored in the DB and for some reason the tempdb items used for the session state get dropped anytime the server restarts. Not only do I need to recreate the items, but I also have to recreate the User mappings to tempdb. I have a script that does it, but I can't figure out how to run it on SQL startup -- Use TempDB use tempdb go -- Create Temp tables if they don't exist IF

问题 I have a site running in IIS 7.5 ASP.NET 4 using MySQL Connector 6.7.4, I am trying to set it up to store session state in my database. It works fine to start with (I can store the state). But when I leave my browser open for a long time and then tries to refresh a page I get the following error: Duplicate entry 'jouwlxjdufet2fyvf4cwefn2-1' for key 'PRIMARY' Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more

问题 I have a script which is meant to finish the current session and start a new one. There is a segment of code I use and it works fine on my development computer. However, when I posted it to the production server, the session id is constantly remaining the same. The following is my code for restarting the session: session_start(); $_SESSION = array(); $_POST = array(); $_GET = array(); if (ini_get("session.use_cookies")) { $params = session_get_cookie_params(); setcookie(session_name(), '',

问题 The native PHP Session functionality is great, but it's ultimately a singleton. There are times when you need to maintain state for multiple apps and in the scope of an already-started session (e.g. in an app framework). Technically one can stop/restart a session after changing session_name() , but this is impractical/impossible/unsafe within most apps. Using a shared session.save_path is also not an option if one app stores session data with a non-disk adapter. There's no reason the

问题 Is there an elegant solution for synchronizing sessions across multiple ASP.NET applications? I'm sure this could easily be considered a security hole, but there is a 3rd party ASP.NET application involved, for which there is no ability to extend. For this reason, a second [related] site is being developed, but will require direct access to the sessions created on the 3rd party application. As an example, when a user logs in/out of one site, the same operation should occur on the other site.

问题 I am trying to do the following: Anonymous user with a unique key enters a code and clicks 'Start Survey' The button needs to call a plsql process to populate some hidden page items. Once the values are set branch to the survey page which will use the hidden items for filtering results. The Problem No matter what I have tried so far the items set by the process are null when I get to the next page. I assume this is because it did not submit. The way I have it at the moment is: Button

问题 I have a ASP.NET 3.5 website running on Windows Server 2003 and I'm using the ASP.NET State Service to manage sessions. It will appear to be working then I regularly get an error saying my code needs to have version 2.0 of the State Service running to work (I think that's what it said, I've temporarily switched back to storing sessions InProc). Refresh the page and the error goes away (for a bit, it's bound to come back). So I looked at the properties of the ASP.NET State Service in the

问题 I use spring security3 and spring mvc3 to build an web project. There is page called index.jsp, login user name and online user count will be displayed on the top of this screen. There are 2 ways to login the system: from login page, use default configuration post by 'j_spring_security_check' ajax login with manually authentication When I use login page to login into index page, both of count of online information and user name show correctly. But when I use ajax login (manually authenticate)

问题 Note that "singleton" used in slightly uncommon sense - "object visible as single instance like HttpContext.Current" unlike normal "object with one shared instance". I make use of a singleton type of UserContext class for my asp.net MVC applications. This class allows me to store user data as a strongly-typed session object. I ran across this CodeReview question and wondered if it was necessary to be concerned about thread safety in this application context. Here's a simplification of my code

问题 I have written an application in ASP.net, that is designed to let the user add records to a database. The page is set up that when a user adds a record, the ID number of the newly added record is set in session, the page Response.Redirects to a "Thank you for submitting" page, then redirects back to the original page to allow further edits. Users can also use the Back button on this screen to go back to the original record adding page, which allows them to make edits to the data. However, I