The AddToken attribute of the CFLOCATION tag simply appends the CFID and
CFTOKEN values to the URL that the CFLOCATION tag is sending the browser to.
You would use this if you are using client management and want the CFID and
CFTOKEN values passed around on the URL. Using cookies is the preferable way
to track a client session and then you can set AddToken to No.
EXAMPLE:
If your CFAPPLICATION tag looks like this...
<CFAPPLICATION name="APP_NAME" sessionmanagement="no" clientmanagement="yes"
setclientcookies="yes">
....you can set the AddToken to "No".
But if your CFAPPLICATION tag looks like this...
<CFAPPLICATION name="APP_NAME" sessionmanagement="no" clientmanagement="yes"
setclientcookies="no">
....then you will need to set AddToken to "Yes" to track this client session.
-----Original Message-----
From: Clint Tillerson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 12:57 PM
To: Fusebox
Subject: cflocation, addtoken = yes||no
Does the "addtoken" attributue of <cflocation> refer only to their
display in the URL? i.e., Will your site perform the same
regardless how you set this attribute? If you set addtoken = No,
are they still passed? In development, this seems to be true, but
I'm worried whether sessions will be lost or confused in production
with multiple users. If it doesn't matter whether you set it Yes or
No, why would anyone ever set addtoken = yes?
Thanks for your feedback!
------------------------------------
Clint R. Tillerson
Meteorologist/Programmer
Pacific Environmental Services, Inc.
5001 South Miami Blvd.
PO Box 12077
RTP, NC 27709
(919) 941-0333
Fax: (919) 941-0234
------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
