Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 51409 invoked by uid 500); 19 Nov 2001 18:46:36 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 51392 invoked from network); 19 Nov 2001 18:46:35 -0000 Message-ID: <3BF95E56.2060503@sseriga.edu.lv> Date: Mon, 19 Nov 2001 20:32:38 +0100 From: Alfredas Chmieliauskas User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801 X-Accept-Language: en-us MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: Cache Problem Using MSIE5.0 And location.href References: <3BF918FA.1090806@netscape.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Peter Hargreaves wrote: > Hi Folks, > > My solution uses browser frames. It seems to be OK with Netscape > Explorer 4.0 but I have a cache problem with MS IE 5.0. I'm not sure > if it is an MS bug or something to do with Cocoon. Any advice would be > very welcome. > > One of my frames contains a directory listing. When it loads the body > onload property runs some javascript to set the location of my content > frame to the last item in the directory. > > > > By viewing IE Internet Options > Temporary Internet Files, I can > confirm that the onload command loads the cache copy of the file > instead of a new copy from the server. This is despite the fact that > the cached file is listed as Expires=None, and Last Modified=None. > Following the failed attempt the Last Accessed time is later that the > Last Checked time. Surely this should be impossible!? Does this prove > that it is an MS IE problem or could it be the way I am using Cocoon? MS IE definately has problems with caching ;-). Try setting the response headers in your cocoon page response.setHeader("Expires", "Mon, 01 Jan 1990 00:00:00 GMT"); // this "hack" usually works ;-) response.setHeader("pragma", "no-cache"); and the following meta tags in your document: this should definately solve your problem (on all browsers). Alfredas > > > Can anybody help please? > > Many thanks > Peter. > > P.S. Cocoon 2 is brilliant - I like it very much. > P.P.S. I'm using: NT4.0, Jdk1.3, Tomcat 3.2.1, C2rlc2. > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: