Glad you're making progress. The headers are HTTP headers, which are not displayed by browsers. You'd need a command-line HTTP GET tool, or a recording proxy, or a packet sniffer to see them.
Chris Norloff ---------- Original Message ---------------------------------- from: Brian Scandale <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Wed, 24 Jul 2002 12:21:02 -0700 >Chris, > >Thanks. Finally! This worked... but only in IE6.0 . . . Netscape 4.07 and 6.2.3 still >give the post expired in the cache warning. I expect they do not recognize the >cache-control directive. My reading this morning indicates it is a directive for >http/1.1 > >An odd aside... when viewing the source in the browser... the cache-control directive >does not show up. However without it the operations are NOT cached by the browser. > > > >At 06:10 AM 7/24/02, you wrote: >>We use >><cfheader name="cache-control" value="private"> >>to allow private caching (browser) but not public caching (proxy). It's worked well >for us. Look in an HTTP book for allowable commands. >> >>The javascript history function gave us a lot of problems because our site is >encrypted (https) and Internet Explorer thinks javascript is not secure so throws up >a pop-up window "alerting" the user that the requested page has a mix of secure and >non-secure items. >> >>Chris Norloff >> >>---------- Original Message ---------------------------------- >>from: Brian Scandale <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>date: Tue, 23 Jul 2002 23:24:03 -0700 >> >>>Nope, just scoured the source again... not a one... nothing. >>> >>>At 06:58 PM 7/23/02, you wrote: >>>>Are you using any of the below cache control tags? >>>> >>>><META HTTP-EQUIV="Expires" CONTENT="Mon, 06 Jan 1990 00:00:01 GMT"> >>>><META HTTP-EQUIV="Pragma" CONTENT="no-cache"> >>>><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"> >>>> >>>><META HTTP-EQUIV="Cache-Control" CONTENT="0"> >>>> >>>><CFHEADER NAME="Expires" VALUE="Mon, 06 Jan 1990 00:00:01 GMT"> >>>><CFHEADER NAME="Pragma" VALUE="no-cache"> >>>><CFHEADER NAME="cache-control" VALUE="no-cache"> >>>> >>>>Joe >>>>Certified Advanced ColdFusion Developer >>>>[EMAIL PROTECTED] >>>> >>>>-----Original Message----- >>>>From: Brian Scandale [mailto:[EMAIL PROTECTED]] >>>>Sent: Tuesday, July 23, 2002 8:49 PM >>>>To: CF-Talk >>>>Subject: cfmx and browser cache issue >>>> >>>> >>>>I've been working a problem for about 3 weeks now... with no luck. I am >>>>having a hard time believing I am the only one affected by this. At first >>>>that is what I thought... >>>> >>>>I am open to any and all ideas. I now think it is a problem with CFMX. I can >>>>open access to the application for those who want to see for themselves what >>>>I will describe below. >>>> >>>>I have an application with more than 300 of this tag embedded in it: >>>><input type="Button" value="GoBack" onclick="javascript:history.back();"> >>>> >>>>Using CF5 and deployed on (Redhat/apache 1.3) and (Win2K/IIS) I have never >>>>had a problem backing up across previously posted results. Just click on the >>>>GoBack Button and away we go... back. >>>> >>>>Now I upgrade to CFMX and I get this on both the linux and the win >>>>platforms: This document resulted from a POST operation and has expired from >>>>the cache. If you wish you can repost... blah blah blah. >>>> >>>>It happens in IE5,IE5.5,IE6.0,Netscape4.07. >>>> >>>>I can either rewrite the application to never goBack or try and fix this. >>>> >>>>Can I be the only one who experienced this on the CFMX upgrade??? >>>> >>>>Anyone want to look where I have been looking for weeks now? >>>> >>>>Thanks, >>>>Brian >>>> >>>> >>>> >>> >> > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
