Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Message-ID: <C9537954CC23D411A051009027AC834EF68102@MAILBOX>
From: Henry Yeh <hyeh@Scheduling.com>
To: "'tomcat-dev@jakarta.apache.org'" <tomcat-dev@jakarta.apache.org>
Subject: RE: Patch to bug #345 complete ?
Date: Mon, 20 Aug 2001 11:48:31 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"


does any one have the bug # for the "304 Not Modified" bug 
of tomcat ?

thanks,
Henry

-----Original Message-----
From: Craig R. McClanahan [mailto:craigmcc@apache.org]
Sent: Monday, August 20, 2001 11:35 AM
To: tomcat-dev@jakarta.apache.org
Subject: Re: Patch to bug #345 complete ?


On Mon, 20 Aug 2001, Justin Erenkrantz wrote:

> On Mon, Aug 20, 2001 at 10:54:43AM -0700, Craig R. McClanahan wrote:
> > I'm not sure I would make quite so blanket a statement as that.  If the
> > servlet itself understands that the content it produces changes rarely,
it
> > can improve performance by respecting If-Modified-Since values.  To make
> > this worthwhile, though, it will also need to control the value sent for
> > the "Last-Modified" header, which you can do by overriding the
> > getLastModified() method of HttpServlet.
> 
> True - you are correct.  But, this wouldn't be something that Tomcat 
> could do by default - this would require that the servlet itself 
> handle this and have appropriate logic via getLastModified().  
> The servlet can handle it, but that's user code not Tomcat code.  

Agreed.

On my earlier statement, I should have pointed out that the automatic
handling Tomcat 4 does is when serving static resources only.

> -- justin
> 
> 

Craig