[
https://issues.apache.org/jira/browse/SOLR-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874021#action_12874021
]
Yonik Seeley commented on SOLR-1936:
------------------------------------
In the interest of not destroying information, we should probably not map
U+2028 to "\n", but instead encode it as \u2028
> Json output Incorrect escaping Unicode Character 'LINE SEPARATOR' (U+2028)
> --------------------------------------------------------------------------
>
> Key: SOLR-1936
> URL: https://issues.apache.org/jira/browse/SOLR-1936
> Project: Solr
> Issue Type: Bug
> Components: Response Writers
> Affects Versions: 1.4
> Reporter: Robert Hofstra
> Fix For: 1.4
>
> Attachments: patch-SOLR-1936-test.txt, patch-SOLR-1936-TRUNK.patch,
> patch-SOLR-1936.txt
>
>
> The Unicode Character 'LINE SEPARATOR' (U+2028) is not escaped in json
> response, resulting in a exception when evaluting this response on a client
> (in our case a firefox 3.0.19 , chrome 5.0.375.55 beta) webbrowser.
> Evaluting a response with this U+2028 char results in a 'unterminated string
> literal' error in firefox.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
