http://nagoya.apache.org/bugzilla/show_bug.cgi?id=154 *** shadow/154 Fri Mar 9 14:17:12 2001 --- shadow/154.tmp.7453 Fri Mar 9 14:17:12 2001 *************** *** 0 **** --- 1,33 ---- + +============================================================================+ + | Setting Last-Modified within doGet results in duplicate Last-Modified head | + +----------------------------------------------------------------------------+ + | Bug #: 154 Product: Tomcat 3 | + | Status: UNCONFIRMED Version: Nightly Build | + | Resolution: Platform: All | + | Severity: Normal OS/Version: All | + | Priority: High Component: Servlet | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
