> The last user to log into the system has their details available to all other users logged in.
Be really specific about you mean here, and give a few details about the deployment environment. - What session information appears to be "shared" by the users? - Can you demonstrate the session problem in a simple example that does not involve security in any way? One user hits page that puts something in session, second user hits page that puts something in session, first user can see second user's crap on a page that shows contents of the session. Something like that. - If not, are you using container-managed security (as defined in the servlet spec) or something else? - Is there a web server between the users and the app server? -Max ----- Original Message ----- From: "Ciaran Hanley" <[EMAIL PROTECTED]> To: "Struts User Mailing List" <[EMAIL PROTECTED]> Sent: Monday, March 08, 2004 4:48 PM Subject: Cookies And Session Problems Hey, I am writing an app but am having session problems. The last user to log into the system has their details available to all other users logged in. I haven't much of an idea about session control can anybody give some pointers in the right direction? >From reading I am thinking url rewriting is the way to go about it, but cant find any good code snippets to get me started. Also, if caching is disabled does this mean that cookies won't be stored on the hard drive? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
