According to Geoff Hutchison:
> At 9:49 AM +0100 1/31/01, Pfennich Michael wrote:
> >the problem is, that the modification time in the htsearch
> >output is always set to 1970-01-01 !!! (details in
> >my mail in december, and in the bug database as bug id 969 )
> >[snip]
> >if i change the format to: "%d %b %Y %H:%M:%S" everything works,
> >and the date in search output is correct !!
>
> OK, this is quite helpful. It sounds like your strptime is broken in
> a very strange way. I don't know a very good workaround inside
> ht://Dig itself, though we could certainly write a configure test for
> it. The problem as I would see it is that the underlying libc isn't
> accepting the timezone format.
>
> (Otherwise, why would it give the right date when you give the shorter format?)
>
> Any thoughts?
My understanding was that the standard for HTTP servers requires the
time to be given in UTC/GMT, and so we don't really need to parse the
timezone (or possible lack thereof) from the HTTP headers. The 3.1.x
code didn't have any %Z format string in its date parsing, so it seems
to me that if this poses a problem in 3.2, without any good justification
for its presence, it should be taken out. The new date parsing in 3.2
was developped with very little regard for the previous code in 3.1.x,
and all the problems that had already been overcome in that code, and
so we've had to recover lost ground bit by bit in the new code.
--
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
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
