Re: Handling Session timeout with ajax
Re: Handling Session timeout with ajax
- Subject: Re: Handling Session timeout with ajax
- From: Chuck Hill <email@hidden>
- Date: Wed, 28 Jan 2009 17:24:15 -0800
On Jan 28, 2009, at 5:08 PM, Paul Hoadley wrote:
On 29/01/2009, at 11:13 AM, Chuck Hill wrote:
Both of these still produce the same result for me: a redirect to
something like AM.woa/wo/4.0, which it presumably can't find and
so returns Main. I've got logging in Session.terminate(), and
it's not being called.
Using the second variant, if I log the sessionID at the call to
session().savePage(), it's different from the sessionID for the
Main component that eventually gets displayed. So there's no
session termination, but a new session is being created. I don't
know whether this is expected, or part of the problem.
Troublemaker! :-P
I feel like one.
Are you storing the session ID in the URL or in cookies?
And there we have it: URLs.
If in the URL, that is the problem as the redirect URL has no
session ID in it. If it is in a cookie, is the cookie getting
killed somehow?
Changed to cookies, problem solved. Thanks for sorting it out, and
for sticking with me for 31 posts over 5 days. :-) Thanks to Anjo,
Mike and Ray for debugging tips along the way.
Hold on now, that is just a work around, not a solution. The question
now is why ERXRedirect is not putting the session ID in the URL for
you.... And, it is a bug. I have a fix, do you build Wonder from the
source (can you test it if I commit it)?
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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