I did this (rundig -vvv) just after I sent out the mail list question. Indeed, the Content-Type header for the "sonnaxmacfile" (the virtual server that was not processing the indexing) did not include pdf. It appears this virtual server is not recognizing the mime.type file specified in httpd.conf. I expected named virtual hosts to use parameters from httpd.conf unless such parameters were specified differently in the virtual host configuration. But this is not really an htdig issue.
--dick peskin
On Mar 6, 2005, at 3:33 AM, Jim wrote:

On Sun, 6 Mar 2005, Richard Peskin wrote:

I have two nearly identical servers, call named "sonnaxmacfile" and "harvey". I have identical htdig test configuration on each. When I run "rundig" on harvey, I get correct indexing and the searches work. When I run "rundig" on sonnaxmacfile, I do not get a completed indexing. Both systems have identical files for testing and the directories involved are correctly indexed by apache. As can be seen from the rundig -vv output below, on sonnaxmacfile, my pdf files are flagged as "not HTML", and are ultimately discarded by the htmerge.

The only difference between the two systems is that "sonnaxmacfile" is a virtual host, but "harvey" is a "default" (not virtual" host).

Can anyone help me understand what is happening here?

Try bumping up the number of -v's (-vvv perhaps) until the Content-Type
header is included in the output. Then compare the value of that header
for the two servers. The "not HTML" message is generated when the value
provided for content type does not include "text/", is not
"application/pdf", and is not recognized as something the external
parser is able to handle.

Jim




____________________________________
<x-tad-smaller>Richard L. Peskin, RLP Consulting, Londonderry, VT
http://www.rlpcon.com
http://www.caip.rutgers.edu/~peskin</x-tad-smaller>

Reply via email to