Description of problem:
When ht://dig indexes the local directory tree, the index entries flood the
response of the eventual search. This makes it very difficult to obtain quality
Version-Release number of selected component (if applicable):
Use Ht:/dig ( rundig ) to index a directory tree of documents. Once the
indexing is complete, then make a query against the local http server. The
result is generally flooded with filenames that have marginal relevance.
Steps to Reproduce:
1. Configure local httpd to include directory tree of local documents.
2. Configure and run "rundig" to index the local docs.
3. Make query of words expected to be found.
In many cases, the tquery result just has repeated directory entries simply
because the word has a match in the filenames, but doesn't deliver the files
It would be better to go a level deeper to the files that match, rather than
sections of directiry entries where a filename might match.
This is discussed in the HT://dig website on directory indexing. It is up to
the apache folks to adopt the proposed solution.
The idea is that the directory entries generated would be presented with meta
data which would direct the indexing robot to ignore the directory, but follow
this makes a HUGE difference in the usability of the two packages.
Created attachment 141808 [details]
patch to add robot directive to autoindexing.
Thanks for the patch and report. Could you submit the patch for consideration
upstream at firstname.lastname@example.org?
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.