Frank,
When you use client variables instead of sesssion variables they no longer
"time out" when the browser closes.
This means that if you are using them to check if a person is logged in you
have to take some special actions.
The choices are:
1/ Get the user to log off and delete the cookie yourself at that point.
tricky..
2/ Use your own cookie to see if they are logged on. messy...
3/ Dont let CF write its own cookies but write them for it. You can set them
as session cookies and then client variables will behave like session
variables. neat eh?
Kevin
-----Original Message-----
From: Frank Kosyk [mailto:[EMAIL PROTECTED]]
Sent: 07 September 2001 11:35
To: Fusebox
Subject: RE: URLToken...
Hi Erik,
thanks for your reply! Actually I just installed the new box, there can be
no cookies on it. But it just won't create new CDID, I tried everything, db
storage for the variables and then deleting then manually, registry as
storage and so on, but the application just won't create new ones. Basically
it is not the application, but it is the CF server...
I copied my latest release of the app to a 2nd server and it works
perfectly, so that means, that the code works just fine and that it maybe is
configuration problem... any ideas?
thanks,
Frank
-----Original Message-----
From: Erik Schaareman [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 07, 2001 1:27 AM
To: Fusebox
Subject: Re: URLToken...
Maybe an old cookie from your testsite still exists with an CFID and
CFTOKEN.
I haave had some troubles with users that had old cookies with CFID and
CFTOKEN
on their machine. Even though setclientcookies="no", CF always seems to be
looking
for a cookie. It doesn't set cookies, but it uses automatically old ones.
Try to throw away all your cookies and test your application again.
With kind regards,
Erik Schaareman
----- Original Message -----
From: "Frank Kosyk" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 9:18 AM
Subject: URLToken...
> Hello,
>
> I developed an application using the Fusebox methodology...
>
> I have a funny problem, which I think is not related to Fusebox, but is a
> general CF issue.
>
> I could login one and I was given a CFID and a CFTOKEN, but then the
second
> time I log in it still
> uses the old CFID and the old CFTOKEN..., which means I don't have to
login
> again!Since this is a
> multiple user system, login is mandatory!
>
> Has ever someone had similar problems? I used the Registry, an Oracle
> Database and Cookies as
> storage for the client variables, always the same effect.
>
> The disable gloabal client variable updates option is not checked, so I
> think the server should update my
> variables...
>
> Here is the beginning code of my app_globals.cfm
>
> <cfapplication name="myapplication" clientmanagement="yes"
> sessionmanagement="yes" setclientcookies="no">
>
> Thanks for your help, I will keep looking! We actually have to rollout the
> app on monday at a client and
> the problems just started yesterday, but nobody was changing code at that
> time...
>
> Bye,
>
> Frank
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
