[jira] [Updated] (NUTCH-685) Content-level redirect status lost in ParseSegment

["Sebastian Nagel (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NUTCH-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Nagel updated NUTCH-685:
----------------------------------
    Fix Version/s: 1.17

> 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
>            Priority: Major
>             Fix For: 1.17
>
>
> 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 was sent by Atlassian Jira
(v8.3.4#803005)