According to Gabriele Bartolini:
> I just installed htdig-3.1.2 and encountered some problems with
> modification date. In fact, htsearch is always showing today's date.
>
> Any considerations over it?
There are a few things that can cause this. One is if you set the
modification_time_is_now attribute to true in your htdig.conf, in
which case htdig won't even try to parse the Last-modified header
returned by the server. Another possibility is htdig is unable to
parse the Last-modified header because the server isn't putting it
out in the correct format. Running htdig -vvv should reveal whether
htdig is having trouble parsing the dates. However, none of this
has changed between 3.1.1 and 3.1.2.
What has changed is that htdig will now use the system's own timegm()
function, if the configure script finds it, rather that its mytimegm()
function. This is what converts the time values into a time_t, after
the string has been parsed. If htdig -vvv shows that it's translating
the dates correctly, but not converting them correctly after that, then
your system's timegm() function may be broken.
--
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.
