Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 86081 invoked from network); 30 Sep 2000 05:48:43 -0000 Received: from msp-26-164-174.mn.rr.com (HELO localhost.localdomain) (24.26.164.174) by locus.apache.org with SMTP; 30 Sep 2000 05:48:43 -0000 Received: from fatman (IDENT:nobody@localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id XAA04928 for ; Fri, 29 Sep 2000 23:46:55 -0500 Message-ID: <135653181.970289215407.JavaMail.nobody@fatman> Date: Fri, 29 Sep 2000 23:46:55 -0500 (CDT) From: BugRat Mail System Reply-To: BugRat Mail System To: tomcat-bugs@cortexity.com Subject: BugRat Report #185 has been filed. Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="135649925.970289215379.JavaMail.nobody@fatman" X-Mailer: org.gjt.mail.EnhancedMimeMsg, Organization: The Giant Java Tree, X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N --135649925.970289215379.JavaMail.nobody@fatman Content-Type: text/plain Content-Transfer-Encoding: 7bit Bug report #185 has just been filed. You can view the report at the following URL: REPORT #185 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: low Severity: non-critical Confidence: public Environment: Release: Tomcat/3.3dev JVM Release: JDK 1.2.2 Operating System: FreeBSD OS Release: 3.3 Platform: Intel Synopsis: Setting Last-Modified within doGet results in duplicate Last-Modified headers Description: Within my doGet() routine, I manually set Last-Modified using: setDateHeader("Last-Modified", modificationTime); I also implement getLastModified(). If getLastModified returns a valid value, then the response generated has duplicate Last-Modified headers. Looking at jakarta-servletapi/.../javax/servlet/http/HttpServlet.java, it appears that the service() routine sets a Last-Modified header before calling doGet(), which suggests that setDateHeader() is broken and fails to correctly override the previous definition. I looked through jakarta-tomcat/.../util/MimeHeaders.java and couldn't see what might cause this behavior. --135649925.970289215379.JavaMail.nobody@fatman Content-Type: text/html; name=Report-185.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=Report-185.html Content-Description: DataSource attachment 'Report-185.html' BugRat Report # 185

BugRat Report # 185

Project: Tomcat Release: Tomcat/3.3dev
Category: Bug Report SubCategory: New Bug Report
Class: swbug State: received
Priority: low Severity: non-critical
Confidence: public

Submitter: Tim Kientzle ( kientzle@acm.org )
Date Submitted: Sep 29 2000, 11:46:55 CDT
Responsible: Z_Tomcat Alias ( tomcat-bugs@cortexity.com )

Synopsis:
Setting Last-Modified within doGet results in duplicate Last-Modified headers
Environment: (jvm, os, osrel, platform)
JDK 1.2.2, FreeBSD, 3.3, Intel

Additional Environment Description:

Report Description:
Within my doGet() routine, I manually set Last-Modified using: setDateHeader("Last-Modified", modificationTime); I also implement getLastModified(). If getLastModified returns a valid value, then the response generated has duplicate Last-Modified headers. Looking at jakarta-servletapi/.../javax/servlet/http/HttpServlet.java, it appears that the service() routine sets a Last-Modified header before calling doGet(), which suggests that setDateHeader() is broken and fails to correctly override the previous definition. I looked through jakarta-tomcat/.../util/MimeHeaders.java and couldn't see what might cause this behavior.

View this report online...
--135649925.970289215379.JavaMail.nobody@fatman--