Geoff Hutchison (firstname.lastname@example.org)
Sat, 19 Jun 1999 12:31:12 -0400 (EDT)
On Fri, 18 Jun 1999, Gilles Detillieux wrote:
> last-modified header? I think the way it works now is just plain wrong!
> If there are no objections, I'd like to change it - especially now that
> it's on by default!
It's a bug. I turned it on because we *still* seem to occaisionally get
documents returned with no date. I wanted to flush out the problems with
this since we *should* be using time(0) when no date is returned.
I haven't given much time to tracking down the bug. If you have better
luck, go for it!
> yet not return a last-modified header? If not, then I don't see any
> big advantage to this option. Has anyone ever put it to good use?
This was added at the request of the author of WWWWoffle. The cache can
use ht://Dig to index and search the cache and it only returns a
Last-Modifed header if the server sent one. However, it does honor an
If-Modified-Since header because it passes that on if necessary.
Williams Students Online
To unsubscribe from the htdig3-dev mailing list, send a message to
email@example.com containing the single word "unsubscribe" in
the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Sat Jun 19 1999 - 08:46:32 PDT