Oh sorry, maybe we should change the description then; <property> <name>http.redirect.max</name> <value>0</value> <description>The maximum number of redirects the fetcher will follow when trying to fetch a page. If set to negative or 0, fetcher won't immediately follow redirected URLs, instead it will record them for later fetching. </description> </property>
In my logs I've seen the same thing as the original poster, I always assumed it was due to the policy of not following redirects anymore by default. Before, the default was around 3 or so and if it redirected above that amount an error was printed. I don't remember exactly what it said, but it was a definite "no brainer". ----- Original Message ---- From: Andrzej Bialecki <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, March 9, 2007 2:57:19 AM Subject: Re: Fetch: java.lang.NullPointerException Sean Dean wrote: > You will see that type of error now when the fetch of a document goes beyond > the maximum amount of redirects in your nutch-default or nutch-site.xml files. > > If you didn't change any settings yourself this will be set to 0, in which > case it will not fetch the page but record it for later fetching. > Actually, 0 means "no limit" ... > > It might not be the most informative of error messages, but most other errors > have a more detailed output. Maybe we can get this changed soon if its > possible. > The real reason may be reported in the log files. -- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com
