Hi, folks. There seems to be some discrepancy on the behaviour for
the modification_time_is_now attribute, between what the docs say
and what the code does. The docs say:
This sets ht://Dig's response to a server that does not
return a modification date. By default, it stores
nothing. By setting modification_time_is_now, it will store
the current time if the server does not return a
date. Though this will return incorrect dates in search
results, it will cut down on reindexing from such servers
when doing updates.
In reality, this parameter makes the current time override the
server's last-modified header for the document, if it does return one.
Is this what it should be doing, or should it only do so if there's no
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!
In any case, this cuts down on reindexing only if the server handles
if-modified-since headers. Are any servers likely to handle this header,
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?
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
