You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/06/24 17:26:04 UTC
[jira] [Resolved] (CONNECTORS-1215) Tag parsing in script tags
shouldn't recognize "<" but does
[ https://issues.apache.org/jira/browse/CONNECTORS-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright resolved CONNECTORS-1215.
-------------------------------------
Resolution: Fixed
r1687303 (trunk)
r1687305 (dev_1x)
> Tag parsing in script tags shouldn't recognize "<" but does
> -----------------------------------------------------------
>
> Key: CONNECTORS-1215
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1215
> Project: ManifoldCF
> Issue Type: Bug
> Components: Web connector
> Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.10, ManifoldCF 2.2
>
> Attachments: CONNECTORS-1215.patch
>
>
> User says:
> "There appears to be a bug in the TagParseState when the comparison operator '<' is encountered in the body of a script tag. It appears to get flagged as an open tag and then the next '</' closes it. In my case, the next '</' is the script tag. The ScriptParseState chomps everything until it encounters a second </script> tag.
> A live link that demonstrates this bug is here:
> http://www.prnewswire.com/search-results/news/Google%252C%2520Inc.-30-days-page-1-pagesize-20
> The '<' near line 2826 in the script body that begins near line 2759 begins a new tag 'arraykeywords.length' which gets closed by the '</' in the closing script tag. The ScriptParseState chomps all the html until it sees the end script tag near line 3385.
> At the moment, I'm not sure of a solution other than pushing the script tag handling up to the TagParseState and treating it like CDATA is."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)