According to Geoff Hutchison:
> Not to drown the original question (which was on reducing HTTP load), but
> you can also index file:// URLs with the 3.2 development code (e.g. the
> snapshots).
>
> But yes, the current production version will not directly index a file
> system.
Unfortunately, it seems to me that the original question really did get
completely drowned out. Steve, Noel and Fred seem to be interpretting
Brian's question completely differently that what I'm almost certain
Brian was really asking. Brian never said anything about indexing file:/
URLs, nor about indexing pages that are not linked from the start_url.
He simply wanted to index through the local file system rather than
going throught the HTTP server. Saying you can't do this in 3.1.5 is
completely misleading! I've been doing this since 3.1.0b1! This isn't
an issue of non-http URLs or hidden directories, so why cloud the issue
by saying you can't do something entirely different from what the original
question was asking?
As Brian was having problems with getting local_urls to work, it
might be more useful to point out the limitations of this attribute.
It only works with static pages with a very limited set of file name
extensions - .html, .htm, .txt, .asc, .pdf, .ps and .eps - anything
else makes htdig fall back to the HTTP server. This is explained in
http://htdig.sourceforge.net/attrs.html#local_urls, so a careful reading
of this should help out.
--
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]>
Information: http://lists.sourceforge.net/lists/listinfo/htdig-general
FAQ: http://htdig.sourceforge.net/FAQ.html
