You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2009/02/06 11:11:59 UTC
[jira] Created: (NUTCH-685) Content-level redirect status lost in
ParseSegment
Content-level redirect status lost in ParseSegment
--------------------------------------------------
Key: NUTCH-685
URL: https://issues.apache.org/jira/browse/NUTCH-685
Project: Nutch
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Andrzej Bialecki
Assignee: Andrzej Bialecki
When Fetcher runs in parsing mode, content-level redirects (HTML meta tag "Refresh") are properly discovered and recorded in crawl_fetch under source URL and target URL. If Fetcher runs in non-parsing mode, and ParseSegment is run as a separate step, the content-level redirection data is used only to add the new (target) URL, but the status of the original URL is not reset to indicate a redirect. Consequently, status of the original URL will be different depending on the way you run Fetcher, whereas it should be the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.