Ridiculous last-modified dates...

["Robert S. Thau" <rs...@ai.mit.edu>]

A thought --- a saner way to deal with this particular problem might be
to disbelieve any last-modified date which is in the future (e.g., do
something like:

     if (r->finfo.st_mtime > now) r->finfo.st_mtime = now;

suitably modified for whatever your code really looks like, before
setting the headers)...

rst

Re: Ridiculous last-modified dates...

[Brian Behlendorf <br...@organic.com>]

On Tue, 15 Aug 1995, Robert S. Thau wrote:
> A thought --- a saner way to deal with this particular problem might be
> to disbelieve any last-modified date which is in the future (e.g., do
> something like:
> 
>      if (r->finfo.st_mtime > now) r->finfo.st_mtime = now;
> 
> suitably modified for whatever your code really looks like, before
> setting the headers)...

What does this give?

I think this "problem" can be solved on the browser end entirely.  
Remember that there's another standard HTTP response header, "Date", that 
the browser can use to do a sanity check/"tare" on the last-modified header.

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com  brian@hyperreal.com  http://www.[hyperreal,organic].com/