Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 23221 invoked from network); 17 Jun 2004 18:31:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Jun 2004 18:31:07 -0000 Received: (qmail 46451 invoked by uid 500); 17 Jun 2004 18:30:52 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 46418 invoked by uid 500); 17 Jun 2004 18:30:51 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 46285 invoked by uid 99); 17 Jun 2004 18:30:48 -0000 Received: from [66.45.6.69] (HELO mail.webslingerZ.com) (66.45.6.69) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 17 Jun 2004 11:30:48 -0700 Received: from webslingerZ.com (fw.webslingerZ.com [66.45.6.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webslingerZ.com (Postfix) with ESMTP id 672DA1836B; Thu, 17 Jun 2004 14:30:26 -0400 (EDT) Message-ID: <40D1E33C.3070603@webslingerZ.com> Date: Thu, 17 Jun 2004 14:30:20 -0400 From: Chris Rossi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en, it MIME-Version: 1.0 To: Tomcat Users List Subject: Tomcat 4.1.30 does not respect Date header Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello. I am using Tomcat 4.1.30, with java 1.4.2 on a Readhat linux server. I was going to submit a bug report, but I noticed the bug tracker only goes through version 4.1.9. Is that bug tracker still being used? Should I still submit bugs to it? Anyway, I am implementing an HTTP Cache filter using the Java Servlet Filter API. The HTTP spec (ftp:/ftp://ftp.isi.edu/in-notes/rfc2616.txt) requires that a cached response set the "Date" response header to the date/time that the response was generated. In my servlet filter I accomplish this by calling: response.setDateHeader( "Date", timestamp ); When I look at the actual HTTP generated response I'm finding that my attempt to set the "Date" header is being ignored and the date of the header always reflects the time "now". So when my filter returns a cached response to the request, the Date header does not reflect the time the cached response was created and my code ends up violating the HTTP spec and breaks the manner in which the client should be calculating the freshness of the requested resource. This behavior is correct the majority of the time, however, there are cases, like this one, where the programmer needs to explicitly set the Date header. Do the developers agree with me that this is a bug, or am I wrong somewhere in my reasoning? Please let me know. Thanks, Chris Rossi --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org