According to Jim Cole: > You will probably want to remove your current database and rerun htdig > (or add the -i option, which should do the same). The included output > corresponds to an update dig against a document that is reported as > being unmodified since the last dig. Since it appears unchanged, it is > not reindexed, and thus little in the way of useful output is generated. > > Jim > > On Friday, February 21, 2003, at 10:31 AM, [EMAIL PROTECTED] wrote: > > Header line: HTTP/1.1 304 Not Modified > > Header line: Date: Fri, 21 Feb 2003 17:25:24 GMT > > Header line: Server: Apache/1.3.24 (Unix) mod_ssl/2.8.8 OpenSSL/0.9.6c > > FrontPage/4.0.4.3 > > Header line: Connection: close > > Header line: ETag: "16ea00-7bd2-3e4a73a8" > > Header line: > > returnStatus = 2 > > not changed
Yeah. The odd thing is that when rerunning htdig, it's clearly finding this one URL in the database, so it's odd that htmerge claims there's nothing in it. In any case, running htdig -ivvv should give more info about what it's seeing, and why it doesn't see anything beyond this one URL. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
