According to comments left on livedocs, the best way to expire a page is:
<cfheader name="Expires" value="#getHttpTimeString(Now))#">
Although, RFC2616 says "treat other invalid data formats, especially
including the value 0, as in the past".
Furthermore, if you don't want the page to be cached when the back
button is hitL
<cfheader name="Pragma" value="no-cache">
You're right on the buffering thing. CF does use buffered output by
default, with <cfflush> being used to flush it, but I don't think it's a
direct consequence of being bytecode.
Barry Beattie wrote:
<cfheader name="Cache-Control" value= "no-cache">
<cfheader name="Expires" value="#Now()#">
or instead of #Now()#" you can use CreateTimeSpan and put negative
numbers in there
as for Response.Buffer = TRUE which forces the processing to be
completed before pushing anything to the browser, I think this is set
by default in CF and to get around it you use cfflush to progressively
push page content ot the browser...
I can honestly say I've never needed to worry to do this with
CF...perhaps this is the nature of CF compiling to java byte code
instead of the line-by-line interperating that ASP classic used to
do...?
any help?
barry.b
On 2/23/06, Ung, Seng <[EMAIL PROTECTED]> wrote:
Hi:
In ASP, I wrote
Response.Expires = -1
Response.Buffer = TRUE
Do we have something like these in Coldfusion MX 7.01?
Thank you
Seng
--
Haikal Saadh, Applications Programmer
Teaching and Learning Support Services
K405, Queensland University of Technology, Kelvin Grove Campus
[EMAIL PROTECTED], 3864 8633
CRICOS No. 00213J
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/cfcdev@cfczone.org
