On Wed, Sep 01, 1999 at 09:36:57AM -0500, Gilles Detillieux wrote:
> The local_urls processing only works on files with .html or .htm suffixes.
> If you're trying to index anything else, htdig will go to the server, so
> it can determine the Content-Type. Could this be the problem you're running
> into? Your local_urls line looks fine to me, provided that you did specify
> the correct directory.
Hmmm. Most of my URLs in documents point to directories (so the index.html
gets read), e.g. <a href="/some/subdir"> . Are you saying that ht://Dig
reads the first index.html from the filesystem, then sees all these non-
html URLS and starts using the HTTP requests? If so, is there any way
around this besides changing my URLs (or search engines)? A patch maybe?
And if I decide to go ahead and let it make all the HHTP requests, how can I
get it to authenticate itself? We have many many areas, some with different
usernames and passwords. Is this possible? This is why I was leaning
toward the filesystem approach.
Thanks for your help folks!
--
Paul Keck [EMAIL PROTECTED] http://www.coe.uga.edu/~pkeck
Univ. of Georgia- College of Education ftp://ftp.coe.uga.edu/users/pkeck
Office of Information Technology (OIT) mailto:[EMAIL PROTECTED]
--Opinions mine, not OIT's.-- Go fighting anomalocaridids!!!
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word unsubscribe in
the SUBJECT of the message.
