Have you verified that the page sent by tomcat 3 actually has those headers set? It maybe that the browser doesn't even get those headers under tomcat3 (a bug). For what its worth, Cache-Control and Expires aren't browser directives...they are cache (inline cache, proxy cache, etc) directives. I think the RFC is 2616.
Accroding to this: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21 the date in the Expires header must be in RFC1123 format, I don't think "-1" is valid. What is the browser setting? Is the browser set to demand a fresh page on every request? John Turner [EMAIL PROTECTED] -----Original Message----- From: Max Z. [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 18, 2002 10:40 AM To: [EMAIL PROTECTED] Subject: Caching problems Sorry for hammering, but this is important. I have both tomcat 3 and tomcat 4 installed. I have an application running with a few jsp files. I am trying to make sure the browser does not cache the pages. So I use the following code: response.setHeader("Cache-Control","no-cache"); response.setHeader("Pragma","no-cache"); response.setDateHeader("Expires",-1); When I run this under tomcat 3, these lines have no effect and pages are cached in the browser. When I run this under tomcat 4, these pages are not cached and forces the user to reload. The problem is that the environment in which this app will be running is running tomcat 3. Is this a feature or a bug? Any reasons why this is happening ? Is there any way to make it work? Thank You Max -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
