> > Error Occurre > > d While Processing Request</TITLE></HEAD><BODY><HR><H3>Error Occurred While > > Proc > > essing Request</H3><P> <TABLE BORDER><TR><TD><H4>Error Diagnostic > ... > > It is not htdig that is generating these messages. Instead, these are > pages being returned by the site(s) you are trying to index. All > that htdig is doing is trying to parse and index the results returned > by the server. At this point, I don't see anything that indicates > that htdig is doing anything other than what it is intended to do. > > > in addition to the sets of lines like with four "v"'s which seem to be > > spelling out one word per line what the additional message is saying. > > The one word per line that you are referring to is just diagnostic > output generated by htdig as it parses out each individual word it > finds in the response from the server being indexed. Again, this is > normal behavior (when verbose output is enabled) and the words > themselves are coming from the server you are trying to index, not > htdig. > > > Does this provide a clue to the origin of the errors? TIA. > > The origin of the errors is the site you are trying to index. It > appears that the site is attempting to generate some dynamic output, > failing in the content creation, and responding in a rather > ungraceful manner (i.e. no appropriate status code to let a client > know that the intended page creation failed).
> Exactly. It's Coldfusion that's to blame. A useragent that does not > begin with "Mozilla/n.n" where n.n is in the range 0 to 4.9 will cause > this error. A search on Google for the "Error Occurred While > Processing Request" message produced 232,000 hits. And Google spiders > use "Googlebot/2.1 (+http://www.googlebot.com/bot.html)" as their > useragent. > > I have sent a message to Macromedia support -- but they'll probably > ignore it because I'm not a customer :-( Thanks for your responses. How were you able to distinguish the error message I reported from one generated by ht-Dig? The same Web pages have been and are still being processed by ht-Dig version 3.1.5 without these errors. What is version 3.2.0b5 doing differently? It was because the earlier version of ht-Dig didn't produce these errors that I thought that it might be something in the new version. Even if the real source of the errors is the Web pages, there must be something different in version 3.2.0b5 from version 3.1.5 that is part of the reason we're getting these errors with the new version. In my latest message on the topic to the list, I reported that searches on the database can result in either the correct result or erroneous results, including not reporting pages that should be reported or reporting pages with an error message in the htsearch output similar to the error message returned by htdig. Does htdig put these error messages it generates in the databases where htsearch finds them? Also, why are some pages not reported by htsearch which should be reported? The tests I ran suggest (but don't prove) that the key difference between reporting matching pages and not doing so is that the search terms which lead to reports are found in the top-level page of the URL given as argument to htdig while search terms which lead to the htsearch report of no matching pages when in fact there are some aren't in the top-level page. Does the error returned by htdig from some pages explain this or is it an independent issue? TIA. Douglas ======== Douglas Kline [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
