• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Session Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Session Question


  • Subject: Re: Session Question
  • From: Jean-François Veillette <email@hidden>
  • Date: Tue, 8 Feb 2005 18:22:14 -0500

My guess (not verified), is that if there is a cookie with a valid id, then it will use it to access the valid and existing session.
Look at the generated cookies, maybe the cookie's path is defined like "... WebObjects/Test.woa/" you are just missing the last '/' in the url, causing the cookie to not match ? Log the cookies sent/received, my first guess would be that the cookie is not sent.


Another reason why this could happen is related to instance number. If you have more than one instance of the running app, then the wo adaptor (the apache adaptor for example) would route a request to :
http://www.mydomain.com/cgi-bin/WebObjects/Test.woa
to a specific application instance, it's the adaptor's choice, depending on load policy.
So a first request would give you the first application instance (...Test.woa/1/wa/default) where a second hit to the same adress would give you the next instance (...Test.woa/2/wa/default).
Obviously, if session are not shared, then even if the cookie is there, the sessionID won't match a per instance session number, so you will get a new session on your new app instance.


To work on this, look around :
1- persistent session store, so no mather which app instance you get, your sessions are shared
2- work on the woadaptor, look for a way to have an application instance number ( in the cookies, along with the session id ), so that the adaptor will route the request to the same app instance.


- jfv

Le 05-02-08, à 16:26, Gerald Hanks a écrit :

I have an application called Test that I am developing. I can access the app at http://www.mydomain.com/cgi-bin/WebObjects/Test.woa I have the application set to store session ids in cookies. I can start a session and everything works well until I leave the site and return. If I return by back tracking my session is still active. If I return using a direct action such as http://www.mydomain.com/cgi-bin/WebObjects/Test.woa/wa/default then my session is still active. If I return using the application url http://www.mydomain.com/cgi-bin/WebObjects/Test.woa then a new session is created and I lose all my session information.

Is this the way things are supposed to happen or am I doing something wrong? How can I allow users to leave my webobjects application and return without losing their sessions? My understanding was all I had to do was to store the session ids in cookies.

--gerald

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Session Question
      • From: Chuck Hill <email@hidden>
References: 
 >Session Question (From: Gerald Hanks <email@hidden>)

  • Prev by Date: Re: Session Question
  • Next by Date: Re: Session Question
  • Previous by thread: Re: SOLUTION?: Session Question
  • Next by thread: Re: Session Question
  • Index(es):
    • Date
    • Thread