[ https://issues.apache.org/jira/browse/NUTCH-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202460#comment-13202460 ]
Markus Jelsma commented on NUTCH-1259: -------------------------------------- I'll comment on it myself then: the code above fixes the issue and adds a proper content-type to parsemeta. Consider the following URL with a very bad content-type: http://kam.mff.cuni.cz/conferences/GraDR/ I'll upload a patch in a minute that sets the detected content type in the metadata instead > TikaParser should not add Content-Type from HTTP Headers to Nutch Metadata > -------------------------------------------------------------------------- > > Key: NUTCH-1259 > URL: https://issues.apache.org/jira/browse/NUTCH-1259 > Project: Nutch > Issue Type: Bug > Components: parser > Affects Versions: 1.4 > Reporter: Markus Jelsma > Assignee: Markus Jelsma > Fix For: 1.5 > > > The MIME-type detected by Tika's Detect() API is never added to a Parse's > ContentMetaData or ParseMetaData. Because of this bad Content-Types will end > up in the documents. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira