Adding an "Expires" header in the past solves this. The browser will
revalidate its cache. Both IE and Firefox send the If-Modified-Since header
and either get the Not Modified response or hit the server-side cache.
I plan to commit changes that set the Expires header in each place that we
currently set the Last-Modified header. There are calls in about 8 places.
I think we need to localize this better.
There is other minor messiness to clean up here too. The millisecond
truncation issue is handled in two different ways. In one place
(PlanetFeedServlet) the code adds 1000 to the millisecond value before
setting the header, effectively rounding up while setting the header. In
most other places it truncates down before comparing; but, it is only using
this logic for the site-wide case. It should use it for individual blogs as
well.
I'll hope to do some cleanup in a separate checkin later.
--a.
----- Original Message -----
From: "Anil Gangolli" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, September 05, 2006 8:02 AM
Subject: Re: problems with 3.0 on IE
I am going to try sending a combination of Expires and Last-Modified and
see if this can induce IE both to send subsequent requests and to include
the If-Modified-Since header. (Will test with Firefox as well). Based on
my reading of the spec, this should work.
