hi, I wouldn't rely on addtoken to be the best method to stop caching - it's
possible another user could pick up a session which isn't their own...
As for addtoken in cflocation and href. The addtoken attribute of cflocation
will only be useful when a cflocation actually occurs, so if you don't
append URLtoken to urls and they click through a href and they don't have
cookies enabled, you're going to lose them...
So, yes you need to addtoken to all hrefs and forms. Also bear in mind that
if you're using session.URLtoken then every reference to it will have to be
locked as readonly. Instead of sprinkling my code with cflocks everywhere I
copy Session.URLtoken into REQUEST.URLtoken in Application.cfm, so only
requiring one lock per page.
HTH.
--
Ben Lowndes, CF Contractor
http://www.lowndes.net/
Currently available for new contracts.
> -----Original Message-----
> From: Nick Texidor [mailto:[EMAIL PROTECTED]]
> Sent: 22 February 2001 00:17
> To: CF-Talk
> Subject: To ADDTOKEN or not
>
>
> Hi,
>
> Just wondering what the opinions were on the list regarding
> setting ADDTOKEN
> to "YES" in a CFLOCATION call?
>
> I've experienced problems with ISP's caching pages before, and
> this has been
> a fix for it. However, there are also some tags that have been
> sent to this
> list about how to stop a page being cached.
>
> Which is the better method?
>
> Also, if you've developed a site and used ADDTOKEN="YES" in all the
> CFLOCATION calls, have you also used the CFID and CFTOKEN
> parameters on all
> the A HREF links??
>
> Thanks
>
> Nick
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
