[
https://issues.apache.org/jira/browse/NUTCH-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535853
]
Dawid Weiss commented on NUTCH-567:
-----------------------------------
Don't mention it. Happy birthday and I hope it'll work for you. If you take a
look at the patch (source) you'll see it's really a trivial change to the
source... I actually looked at how browsers handle such "illegal" URIs (because
all URIs should have & in them to separate parameters, not just an
ampersand) and it seems they use some heuristics to determine what is an entity
and what is not. Look at the test case -- it shows such a nasty situation. The
current patch attempts to resolve URIs in a similar way my Firefox does it.
> Proper (?) handling of URIs in TagSoup.
> ---------------------------------------
>
> Key: NUTCH-567
> URL: https://issues.apache.org/jira/browse/NUTCH-567
> Project: Nutch
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Priority: Minor
> Attachments: tagsoup-1.1.3-uripatched.jar , uri-entities.patch
>
>
> Doug Cook reported that TagSoup incorrectly handles some URI parameters. More
> discussion on the list and at TagSoup's mailing list.
> http://tech.groups.yahoo.com/group/tagsoup-friends/message/838
> I looked at the sources of TagSoup because I'm using it myself (although the
> URIs are not relevant for me). It seems like you can implement a naive
> workaround by remembering the parsing state and just avoiding entity
> resolution. Attached is the patch that does this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
