[
https://issues.apache.org/jira/browse/TIKA-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490702#comment-14490702
]
Hudson commented on TIKA-1519:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #617 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/617/])
TIKA-1519: add charset information for the non-html formats, too: XHTML(s) and
x-asp (tallison: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1672805)
* /tika/trunk/CHANGES.txt
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/html/HtmlParser.java
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/html/HtmlParserTest.java
> 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
>
> Attachments: TIKA-1519.patch
>
>
> 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)
