On Apr 13, 2005, at 11:37 PM, Ryan Tomayko wrote:
>
> Crap. I've run into this issue before. IIRC, when the SCGI piece sent
> a future date back to apache in the Last-Modified header, apache
> didn't like it. I ended up having to subtract a minute from the date
> or something. I could recreate the problem pretty reliably by
> explicitly setting the date to something far into the future.
>


Maybe the default behavior should be to *not* provide the Last-Modified
header.
It seems like this could be turned on for special cases that really
need it.

I'm a little worried about setting the time back a little.
Wouldn't that be a problem if Apache is running on a different host
that is out-of-sync by more than a little?