[
https://issues.apache.org/jira/browse/TIKA-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285003#comment-14285003
]
Luis Filipe Nassif commented on TIKA-1519:
------------------------------------------
For Tika 2.0, maybe Content-Type could be used for both detected and trusted
(override) mediatypes, so we can have only 2 content type keys?
> Don't allow whatever is in http-equiv Content-Type to overwrite actual
> Content-Type in HtmlParser
> -------------------------------------------------------------------------------------------------
>
> Key: TIKA-1519
> URL: https://issues.apache.org/jira/browse/TIKA-1519
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Tim Allison
> Priority: Trivial
> Fix For: 1.8
>
>
> The HtmlParser will overwrite the value of Content-Type in Metadata with any
> value of content in an http-equiv=Content-Type header, e.g.
> {noformat}
> <meta http-equiv=Content-Type content="blah de blah blah">{noformat}.
> or even worse, perhaps:
> <meta http-equiv=Content-Type content="application/pdf">
> Let's capture the content type alleged by the html file in a different key
> from Content-Type; I'd prefer to reserve Content-Type for "text/html;
> charset=X".
> Candidate key/Property: Content-Type-Meta-HTTP-Equiv?
> See TIKA-1514 for example output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
