[TIKA-1519] Don't allow whatever is in http-equiv Content-Type to overwrite actual Content-Type in HtmlParser

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 1.6
• Fix Version/s: 1.8
• Assignee: Unassigned
• Reporter: Tim Allison
• Created: 15/Jan/15 18:03
• Updated: 11/Apr/15 01:47
• Resolved: 11/Apr/15 00:47

Description

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.

<meta http-equiv=Content-Type content="blah de blah blah">

.

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.

Issue Links

• relates to: TIKA-1528 Add an OverrideDetector that overrides other detectors
• supercedes: TIKA-1514 http-equiv content-type extraction should pick first parseable content value