httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: [PATCH] some cleanups and bug fixes
Date Mon, 04 Aug 1997 09:50:14 GMT
I didn't use that exact comment in the commit ... but yeah it is correct,
the only reason that we figure out what now is, is so that we can respect
the part of the standard that says we won't issue a Last-Modified in the
future.  It's just all confusing in the context of the rest of the

If we just took the mtime at face value and assumed the caller did the
appropriate checks on it, then we wouldn't need now at all. 


On Mon, 4 Aug 1997, Rob Hartill wrote:

> >    time_t now;
> >
> >    /* For all static responses, it's almost certain that the file was
> >     * last modified before the beginning of the request.  So there's
> >     * no reason to call time(NULL) again.  But for a slow dynamic
> >     * content generator that writes a file to cache the results, the
> >     * file's modified time can be later than the beginning of the
> >     * request.  now is used to ensure we don't issue a Last-Modified
> >     * with a date in the future.
> is that last sentence correct ?
> I thought this prevented a Last-Modified in the past (relative to
> the real last-modified date), not future.

View raw message