According to Aidan Jones:
> I have installed HTDig successfully. I am able to index
> something (based on the fact that the db files have kb size). However,
> when I add addtl. documents, the kb size does not increase. Also, I do
> not get any search results.
You didn't mention which version of htdig you're running. What do you do
when you add additional documents? Do you add links to these documents
somewhere? Do you rerun htdig and htmerge (or htpurge for 3.2)?
> My question is: how does it resolve the HTTP mapping. I'm operating in
> a Websphere/Netscape
> environment - the difficulty began after I switched to the default
> server on Websphere.
I'm not sure what you mean by the HTTP mapping. htdig uses HTTP to get
documents from a web server, just like a browser does, and it follows
HTML links to other documents. If it's given a directory URL, and
the directory has no index.html or similar "default" document, htdig
will expect the HTTP server to generate the HTML for a directory index
automatically. If the server doesn't, then htdig won't go any further
in that directory. Maybe this difference in server configuration would
account for the change in behaviour you noticed.
> When running the htdig -vvv, the first two header lines indicate the
> following:
> HTTP/1.1 200 ok
> Server: Netscape Enterprise/ 3.6 sp2
>
> Is HTDig attempting to use the Netscape mappings?
> My htdig.conf file has a start_url mapped to the Websphere document
> directory.
htdig is just showing you the headers that the web server returned. It
doesn't do anything with many of them. The Server: header is ignored.
--
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-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
