I want to tear down a user's session (purging all their variables)
and give the user a new session with new user variables and a new
userreference.
I'll need to <@ASSIGN SCOPE="cookie" NAME="Witango_UserReference"
VALUE="@@request$newUserReference">.
How do I generate @@request$newUserRef
that would be
<@USERREFERENCE>
<@ASSIGN SCOPE="cookie" NAME="Witango_UserReference"
VALUE="<@USERREFERENCE>">.
On Mar 14, 2008, at 5:22 PM, William M Conlon wrote:
I want to tear down a user's session (purging all their variables)
and give the user a new session with new user variables and
No, that would not be a NEW userreference, rather the same
userreference that was passed in by cookie.
Here's the flow;
userreference cookie 'abc' is passed to taf
@@user$id and @@user$somedata is known from user reference 'abc'
assign @@request$id == @@user$id
purge us
NO
in the manual
If no user reference number was received
(via the “_userReference” search argument or an HTTP cookie) when
the application file was called, a new number is generated; otherwise,
the
number passed in is returned.
so you clear the cookie and when you call a page without a
use
BUT ... userreference WAS received via cookie 'abc'
Bill
On Mar 14, 2008, at 5:46 PM, Ben Johansen wrote:
NO
in the manual
If no user reference number was received
(via the “_userReference” search argument or an HTTP cookie) when
the application file was called, a new number is generated;
o
I think the only way, is to CLEAR the userref cookie, and let witango
gen.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead
I wrote a test taf to see what purging the various scopes would do,
and the USERREFERENCE is unchanged. So to change it, I would need to
generate a new one to replace the cookie from the browser.
What I was looking for was a hook into the witango USERREFERENCE
generation scheme. Anyway, i
Well, there are 2 issues, but keep in mind I am going from memory.
1. You can't gen a userreference, and you can't fake with an MD5,
because witango uses the usereference to tie it to the correct
instance of witango in the group.
2. You can't use purge on cookie scope. If I remember correct
From: William M Conlon [EMAIL PROTECTED]
Date: Sat, 15 Mar 2008 11:17:53 -0500
To: witango-talk@witango.com
Subject: Re: Witango-Talk: getting a new userreference
> I wrote a test taf to see what purging the various scopes would do,
> and the USERREFERENCE is unchanged. So to change it, I wo
Hi Robert,
That's right, you can't purge a cookie. It can only be given an empty value or
set to expire.
I recall a couple years ago we all had a long investigative thread on this
topic, but of course my fuzzy brain can't remember the precise outcome just
now. But basically I think we found th
thanks all for the thoughts. I remember also that there is special
treatment of the userreference (presumably to avoid predictive
attacks), so I wanted to make sure that I used the server generated
session id, particular for things like load-balancing.
I wanted to do the change in one requ
11 matches
Mail list logo
