If you are about to deploy, I would not do it. There are issues when
introducing no chache-ing in your pages that you would need to solve. The
one that gave me more problems is back/forward buttons in the user browser.
Imagine this
1. Form a.cfm
<cfform action="b.cfm">
<input type=text name="foo" value="var">
<input type=button name="submit">
</cfform>
2. Form b.cfm
<cfquery name="xxx" datasource="yyy">
insert into aTable (aField) values ('#FORM.foo#')
</cfquery>
Thanks for your input. To continue
<a href="c.cfm">go here</a>
3. Form c.cfm
<BODY>
Just nothing.
</BODY>
This is the deal: If you go from a, to b, to c, and then press the back
button to b.cfm you get a problem. This is a copy/paste from IE:
-----
Warning: Page has Expired The page you requested was created using
information you submitted in a form. This page is no longer available. As a
security precaution, Internet Explorer does not automatically resubmit your
information for you.
To resubmit your information and view this Web page, click the Refresh
button
-----
If you press refresh, then you get a double insertion.
This is how I get rid of the problem in a browser friendly fashion. Get
b.cfm as follows (check the uppercase)
<CFIF ISDEFINED("FORM.FOO")>
<cfquery name="xxx" datasource="yyy">
insert into aTable (aField) values ('#FORM.foo#')
</cfquery>
<CFLOCATION ADDTOKEN="NO" URL="#getFileFromPath(getBaseTemplatePath())#">
</CFIF>
Thanks for your input. To continue
<a href="c.cfm">go here</a>
etc, etc. This double insertion problem is not new, and you may have
already dealt with it, but this explorer message will apprear all across
your site if not taken care of. In my organization it was declared the
number-one problem to fix. with 600+ pages it took me a while to remove the
darn IE message completelly.
<Jaime/>
P.S. I would be curious if a fusebox app (mine is not, too late now) can
deal with this CFLOCATIONING easier, but I doubt it with so many actions in
so many distributed files.
> -----Original Message-----
> From: Kay Smoljak [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, November 05, 2000 11:22 PM
> To: CF-Talk
> Subject: CF 4.0.0 and CFHEADER
>
>
> Hi all,
>
> In CFWACK, the only mention of CFHEADER that I can find says "There is
> usually little need to use <CFHEADER> because ColdFusion sets the HTTP
> headers automatically to optimum values" (page 818).
>
> I'm close to deploying a fairly large site on a CF 4.0.0 server. Is this
> statement fairly accurate? Is there any point, for example, in
> specifying a
> CFHEADER "expires now" tag in my app cfm so that proxy servers don't cache
> dynamic pages?
>
> Thanks,
> Kay.
> ______________________________________________________
> Kay Smoljak - HTML/ColdFusion Developer - PerthWeb Pty Ltd
> Internet Solutions for your business!
>
> Level 9/105 St George's Tc - Perth - Western Australia
> Ph: (08) 9226 1366 Fax: (08) 9226 1375 Mobile : 0419 949 007
> Visit Perth online! : www.perthweb.com.au
>
> ------------------------------------------------------------------
> ------------------------------
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
> or send a message with 'unsubscribe' in the body to
> [EMAIL PROTECTED]
>
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
