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