At 8:20 AM -0400 10/21/98, Oliver R Smith wrote:
>I am currently trialling ht://Dig for use on our Intranet.
>
>I know it is possible to index via the file system rather than via HTTP
>and have successfully tested
>this with htdig-3.1.0b1.
>
>What I would like to know is; is it possible to index only via the file
>system, without using http
>at all? If I kill the httpd then the dig fails with the following output:
>> ./htdig -i -v -v -s
You're running into the problem that ht://Dig falls back on HTTP when it
can't figure out how to resolve the URL into a local file. For example,
over HTTP, a URL to <http://www.foo.com/bar> actually becomes a redirect to
<http://www.foo.com/bar/> and the directory is indexed.
It would be nice to kill HTTP alltogether. But what do you do when you
can't resolve the URL? Ignore it completely? I'm not sure what the action
should be if it doesn't have HTTP access. Input is welcome! :-)
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
----------------------------------------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the body of the message.