I have run into a problem where the cache code randomly decides that a
cached entry is stale or that the last modified date is some time in
the future. I tracked it back to the ap_cache_check_freshness code
which does a lot of checking of dates.
Some of this date checking code compares and assign
On Fri, 2002-10-11 at 16:04, Paul J. Reder wrote:
> I have run into a problem where the cache code randomly decides that a
> cached entry is stale or that the last modified date is some time in
> the future. I tracked it back to the ap_cache_check_freshness code
> which does a lot of checking of d
> At first glance, I think there's an even more fundamental problem:
> the code in ap_cache_check_freshness() appears to be mixing times
> measured in microseconds (the result of ap_cache_current_age())
> with times measured in seconds (everything that it gets from the
> HTTP header).
And does th
