Ok,  I know what my problem is with my funky times being returned
by mktime.  mktime is adjusting them +6 hours for my time zone.

I've still got to figure out the functions to convert the user specified
date into UTC
instead of my local time.  This should be relatively minor though.

another issue I'm running into
is that my test web server returns 0's for doctimes because
I've got apache configured to parse every html document... is there anyway
to force apache
to go ahead and return the last modification date of the html document
instead of returning 0 when it comes to parsed html?

I know that sounds a bit silly since theoretically, every document
could change every time it is viewed, but viewing doesnt change the document
modification time...

as an interesting fix for this, couldnt it be possible to assign
a meta tag to go in the document header for the document date?
How difficult could it be to add this, since htdig is already parsing the
meta tags
in the header anyway, right?

Also, could you guys throw out some ideas on how to go about making
the end date work for any size time_t?

What I'm considering is to check the results coming back from mktime.
if a date (either starting or ending) returns a -1 coming out of mktime,
then I could use
0 for the timet_startdate if it was goofy
and 1<<sizeof(time_t)*8-1 if timet_enddate is goofy.



------------------------------------
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.

Reply via email to