I could be wrong in this but I was under the assumption that client
variables were tracked to the user by a cookie, and the client variables
themselves were stored on the server. So unless you are changing the cfid
and cftoken for some reason, the client variables would be completely in
control of the server. Now pages that have dynamic content might be cached
by IE's internet settings, but that's true of ALL VARIABLES not just client.
-Craig
-----Original Message-----
From: Brook Davies [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 10, 2001 5:39 PM
To: CF-Talk
Subject: Client Variable and Internet Caching options
We have a cf app which uses client vars and at various parts of the
application, on pages which displays some info from a client var, the info
being displayed was from old client variables which were no longer being
used.
We could not figure out why this old data was popping up. Client vars are
no stored in memory so where were they coming from we wondered?
As it turns out, our end user using IE 5.5 had their Internet
options/temporary Internet files/ check for new newer version of the stored
page / set to "automatically". This apparently can cause problems with
client variables. All of our pages have the following code in the header,
but it did not seem to matter. has anyone else experienced this? When we
set the option to "Every visit to the page" it works fine.
<meta http-equiv="Expires" content="12 Nov 1994 08:49:37 GMT">
<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="cache-control" content="no-store">
<meta http-equiv="cache-control" content="must-revalida
Brook Davies
Maracasmedia Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
