I've got an oddity on this topic. I have a page that I'm using both the
no-cache headers that Bruce mentioned, as well as the technique David brought
up (I'm using CreateUUID()). On my page, everything is fresh, except for text
fields (<input type=text.....>) of the same name. What I'm actually doing is
running some code against the same page that adds/removes a text field, and
updates present fields.. so where there might be two text fields with same
name, I can hit a button, and it will refresh the page, and add a text field.
The problem is, when it refreshes, the text area fields are the same as before,
but everything else (various whatnot unique form fields) are "fresh". When I
manually refresh, everything looks OK. Any ideas?
--
Billy Cravens
HR Web Development, Sabre
[EMAIL PROTECTED]
"David L. Penton" wrote:
> Another thing to add to that: a cache-buster url
>
> http://www.mysite.com/mypage.cfm?nocache=RndStrOfNumsAndChars
>
> to ensure a different page. Some IE browser builds can still cache the
> page.
>
> David L. Penton, MCP
> Consultant
> "Mathematics is music for the mind, and Music is Mathematics for the
> Soul. - J.S. Bach"
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of [EMAIL PROTECTED]
>
> Thanks Bruce. I appreciate the quick response!
>
> CC
>
> "Sorge, Bruce" <[EMAIL PROTECTED]>@dfwcfug.org on 04/20/2001 04:29:19
> PM
>
> Actually, depending on the browser that is accessing the page, this may not
> work at all. What I do is add these 4 lines to my code:
>
> 1. <META http-equiv="Pragma" content="No-Cache">
> 2. <meta http-equiv="Expires" content="0">
> 3. <cfheader name="Pragma" value="no=cache">
> 4. <cfheader name="cache-control" value="no-cache, no-store,
> must-revalidate">
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> Hello all -
>
> Whats the best method to ensure the user is always getting the latest and
> greatest web page "version", meaning whats the best method for eliminating
> the browser for pulling from cache or history.
>
> Currently we use
>
> <meta http-equiv="Expires" content="Sat, 1 Jan 2000 12:00:00 GMT">
>
> The process is a manager clicks on a employee record to make a pay decision
> and <a href="blahblah.cfm?SSN=#EE_SS.Personnel_ID_Number#" target="_top">
> tells the next page which record to show, the following page is comprised
> of 3 frames. The manager enters a pay decision is sent to a verification
> page, confirms the decision, then is sent back to the employee selection
> page via a cflocation. Then when the manager clicks a new employee some of
> the information from the previous employee is displaying.
>
> Is <CFHEADER NAME="Expires" VALUE="#Now()#"> a better method to ensure the
> latest version of the page is loaded or is there something else that is
> more reliable?
>
> Thanks in advance for your responses.
> Casey Cook
>
> -------------------------------------------------------------------------
> This email server is running an evaluation copy of the MailShield anti-
> spam software. Please contact your email administrator if you have any
> questions about this message. MailShield product info: www.mailshield.com
>
> -----------------------------------------------
> To post, send email to [EMAIL PROTECTED]
> To subscribe / unsubscribe: http://www.dfwcfug.org
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org
