BugRat Report #185 has been filed.

[BugRat Mail System <to...@cortexity.com>]

Bug report #185 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com:8888/BugRatViewer/ShowReport/185>

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.