[
https://issues.apache.org/jira/browse/TIKA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049325#comment-15049325
]
Markus Jelsma commented on TIKA-1808:
-------------------------------------
I see. So whatever parser we use, we (i at least) are still are going to need
configure exceptions for real world crapsites. Is that possible with JSoup at
all? TagSoup allows us to reconfigure the defaults in html.tssl
programmatically via HTMLSchema.
Perhaps we should close this issue and continue at TIKA-1599?
> 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
> Fix For: 1.12
>
>
> 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
(v6.3.4#6332)