[
https://issues.apache.org/jira/browse/TIKA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769222#comment-17769222
]
Tim Allison commented on TIKA-1808:
-----------------------------------
We've migrated to JSoup in 3.x/main.
We are now getting a title in the html that comes from a redirect to the
original site
(https://www.aljazeera.com/news/2015/5/16/russian-rocket-fails-after-launch).
Of course, there's no <div/> tag in within the <head/> element any more...so
that finding is entirely useless!
I think I'll close this for now? "Won't fix" is the right answer? Or, if
there's anything we can do to help with this issue, please let us know.
> Head section closed too eager
> -----------------------------
>
> Key: TIKA-1808
> URL: https://issues.apache.org/jira/browse/TIKA-1808
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.11
> Reporter: Markus Jelsma
> Priority: Major
> Fix For: 1.17, 2.0.0-BETA, 2.1.0
>
>
> XHTMLContentHandler has some logic that closes the head section too early, or
> this is a problem in TagSoup. In this [1] case a <div> element appears in the
> head, causing the head to be closed. Subsequent <head> elements do not appear
> in custom ContentHandlers so i cannot read the document's title, or any other
> meta tags.
> It can be fixed by using a custom HTMLSchema in the ParseContext, e.g.
> schema.elementType("div", HTMLSchema.M_EMPTY, 65535, 0); but this isn't
> really an elegant solution.
> [1] http://www.aljazeera.com/news/2015/05/150516182251747.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
