Guys,
I've discovered another way to kill CFID and CFTOKEN,
1. Call a page which <CFSET > CFID and CFTOKENS to null.
2. Let the page refresh itself by using Meta tag.
My Codes:
<html>
<head>
<meta http-equiv="refresh" content="1; url='index.cfm'" >
</head>
<body>
<h1><div align="center">Logging out. please wait...</div></h1>
<cfset client.cfid = 0>
<cfset client.cftoken = 0>
<cfcookie name="cfid" expires="NOW">
<cfcookie name="cftoken" expires="NOW">
</body>
</html>
I find it quite Interesting - the use will be able to see a message "Logging
out . please wait" kind of message while waiting to be redirected to
home.cfm
FCF
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "CF-Server" <[EMAIL PROTECTED]>
Sent: Monday, March 12, 2001 10:03 PM
Subject: RE: Kill CFID and CFToken (fwd)
> David,
> Are you saying it is better you session (or) client
> variables, but not both. I just am trying to learn what
> the meaning of that was since i am fairly new.
>
> P.S. Thanks for everyones response to the "cf load"
> question i had last week. Your answers were just what I
> needed.
> Thanks,
> Wes_D
> ---------------------- Forwarded Message: ---------------------
> From: Dave Watts <[EMAIL PROTECTED]>
> To: CF-Server <[EMAIL PROTECTED]>
> Subject: RE: Kill CFID and CFToken
> Date: Sun, 11 Mar 2001 14:21:47 -0500
>
> > I have a rather stupid question to ask. Does anybody know how
> > to get rid of the CFID and CFToken?
> > Here's my cfapplication:
> >
> > <cfapplication name="AppBF"
> > clientmanagement="Yes"
> > sessionmanagement="Yes"
> > setclientcookies="Yes"
> > clientstorage="cookie"
> > sessiontimeout="#CreateTimeSpan(0, 0, 120, 0)#">
> >
> >
> > As you can see, I'm using CLIENT scope var to store my CFID
> > and CFTOKEN. I've created another page for the user to LOGOUT
> > The reason behind this: when the user LOGIN back in the future,
> > she can get a fresh pair of CFID and CFTOKEN.
> >
> > In LOGOUT.cfm :
> >
> > <cfset client.cfid = 0>
> > <Cfset client.cftoken = 0>
> >
> > <!---Go back Home--->
> > <cflocation url=home.cfm" addtoken="no">
> >
> > Even after I ran this page, CLIENT.CFID and CLIENT.CFTOKEN are
> > still there!!! Can't seem to get rid of them ... HELP!
>
> CFID and CFTOKEN are maintained directly by ColdFusion; you don't want to
> try changing them.
>
> Instead, if you want to force the user to have a different CFID and
CFTOKEN
> on her next visit, you can simply make sure that the browser doesn't store
> these values persistently. By default, when you use Client or Session
> management, CF issues two cookies to the browser, CFID and CFTOKEN. Also
by
> default, these cookies are persistently stored, so that when the user
closes
> the browser and later reopens it, the two cookies will still exist. You
can
> change this behavior by placing some code like this in Application.cfm:
>
> <cfapplication ... setclientcookies="No">
>
> <cfif not IsDefined("Cookie.CFID")>
> <cflock scope="session" type="readonly" timeout="2"
> throwontimeout="no">
> <cfcookie name="CFID" value="#Session.CFID#">
> <cfcookie name="CFTOKEN" value="#Session.CFTOKEN#">
> </cflock>
> </cfif>
>
> Note that in the above example, the code references the Session scope
> instead of the Client scope. I did it this way since you're also using
> Session variables. You might want to rethink your simultaneous use of both
> Session and Client variables.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> voice: (202) 797-5496
> fax: (202) 797-5444
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
