Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
Mime-Version: 1.0
Date: Tue, 21 Aug 2001 18:28:21 -0400
Message-ID: <0078F9E9.C22202@seagram.com>
From: Jonathan_Pierce@seagram.com (Jonathan Pierce)
Subject: Re[2]: Mozilla and Tomcat
To: tomcat-user@jakarta.apache.org
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part

You can force the response to not be cached by the browser and proxy servers by
setting headers in your jsp response before writing your html response header.
Make sure to explicitly clear your browser cache once after doing this to get
rid of any latent cached pages.

response.setHeader("Pragma", "No-cache");
response.setDateHeader("Expires", 0);
response.setHeader("Cache-Control", "no-cache");

____________________Reply Separator____________________
Subject:    Re: Mozilla and Tomcat
Author: tomcat-user@jakarta.apache.org
Date:       8/21/2001 1:55 PM

At 01:50 PM 8/21/2001, you wrote:
>I've ran into similar problems with Internet Explorer. Not exactly though.
>Basically, I've seen IE display a cached page, even if you have caching
>turned off. What I do is completely exit and restart my browser each time I
>test a change to a servlet.

Yeah, IE has a wicked sticky cache.