Re: You've backtracked to far...
Re: You've backtracked to far...
- Subject: Re: You've backtracked to far...
- From: Stirling Olson <email@hidden>
- Date: Thu, 9 Dec 2004 07:33:17 -0700
Yeah, I agree 100%, which is why I suffer through the problems with
cookie-based sessions. Oh well, if it was all so easy then I guess we
wouldn't have any jobs...
:-)
On Dec 8, 2004, at 8:49 PM, Dov Rosenberg wrote:
The biggest issue with URL based sessions is not being able to
bookmark the
pages very easy. We could us URL rewriting, but that is more difficult
for
non Apache web servers.
Dov
On 12/8/04 5:03 PM, "Stirling Olson" <email@hidden> wrote:
Not for everyone and this is probably too obvious to mention, but
URL-based sessions is one solution to this problem.
On Dec 8, 2004, at 2:55 PM, Chuck Hill wrote:
Yes! That was it! Now I remember. Thanks Dov.
OK, here is the deal: This only happens when storing sessions in
cookies.
The first browser makes a request and gets a response with a wosid
cookie
and component action URLs in the page. The second browser window
(probably
only some browsers, but who knows) does not have the session cookie
(because the window is already open? something else?) so when it
makes
a
request, a new session is created a new wosid cookie sent down.
When a
link in the first window is clicked, it sends the new wosid cookie
but
requests a URL from the original session. WO is unable to restore
the
requested page (it does not exist in the new session) and so it
throws
a
PageRestoration error which is reported as "you backtracked too far".
No, I don't know of a solution to this.
Chuck
At 04:14 PM 08/12/2004 -0500, Dov Rosenberg wrote:
I have seen that occur when someone logs into an app in one window,
but then
they bring up a second window (for the same browser) and login or do
something. If you go back to the first window that is when the error
usually
shows up.
I think it has to do with cookies that are set by WO somewhere along
the
line. It doesn't seem to happen if I open a new browser window with
a
different brand of browser, i.e. Using Safari and Firefox seems OK.
I sometimes see it in our app if I am logged into our management
console in
one tab, and then open a new tab and go to a web site and
authenticate
myself in the web site. If I go back to the management console and
do
something I usually get the same error.
When I do demo's I just use 2 different browsers and avoid the
problem.
I would be interested in a better solution.
--
Dov Rosenberg
Conviveon Corporation
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
_______________________________________________
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:
dov.rosenberg@conviveo
n.com
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