tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BugRat Mail System <>
Subject BugRat Report #185 has been filed.
Date Sat, 30 Sep 2000 04:46:55 GMT
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
   Release: Tomcat/3.3dev
   JVM Release: JDK 1.2.2
   Operating System: FreeBSD
   OS Release: 3.3
   Platform: Intel

Setting Last-Modified within doGet results in duplicate Last-Modified headers

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
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/ and couldn't
see what might cause this behavior.

View raw message