yes. I analyzed the HTTP header that's being sent and received by the
browser.
If-Modified-Since messages are sent to tomcat, and we are dealing with
static files here (javascript and images).
So is tomcat doesn't have the '304 behavior' for static files ? It does
send back 'last-modified' date information in the header, and that ALWAYS
matches the 'If-modified-since' date. Are we looking at another tomcat
date bug here ?
thanks,
Henry
-----Original Message-----
From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 20, 2001 10:11 AM
To: [EMAIL PROTECTED]
Subject: Re: Patch to bug #345 complete ?
On Mon, Aug 20, 2001 at 09:18:53AM -0700, Henry Yeh wrote:
>
> I have noticed that after applying the patch the date is now
> included in the tomcat HTTP response header, but it still
> does not send back "not modified 304" if the file requested
> hasn't been modified since the date specificed by the request ...
>
> anyone has any ideas on how to fix this ? thanks !
Are you sending If-Modified-Since? That doesn't look like it'd work
in Tomcat.
The 304 behavior doesn't apply to dynamic data as it is *always*
regenerated. So, I'm not even sure if you'd want it. You definitely
don't want to look at the date on the jsp file as that tells you
nothing (unlike static content).
Static content is a different story, but if you are serving static files
from Tomcat, you probably want a real HTTP server in front of it.
-- justin
