Uploaded image for project: 'Nutch'
  1. Nutch
  2. NUTCH-685

Content-level redirect status lost in ParseSegment

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.0.0
    • 1.21
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

          Blocked

          Bug - A problem which impairs or prevents the functions of the product. NUTCH-2261 ParseSegment job does not pass metadata for content-level redirects

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              Unassigned Unassigned
              ab Andrzej Bialecki
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: