lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2520) JSONResponseWriter w/json.wrf can produce invalid javascript depending on unicode chars in response data
Date Mon, 16 May 2011 18:38:47 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034187#comment-13034187
] 

Benson Margulies commented on SOLR-2520:
----------------------------------------

I'd vote for the later. I assume that there is some large inventory of people who are currently
using json.wrf=foo and who would benefit from the change. However, I have limited context
here, so if anyone else knows more about how users are using this stuff I hope they will speak
up. Sorry not to have been fully clear on the first attempt.


> JSONResponseWriter w/json.wrf can produce invalid javascript depending on unicode chars
in response data
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2520
>                 URL: https://issues.apache.org/jira/browse/SOLR-2520
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Benson Margulies
>
> Please see http://timelessrepo.com/json-isnt-a-javascript-subset.
> If a stored field contains invalid Javascript characters, and you use the query option
to ask for jsonp, solr does *not* escape some invalid Unicode characters, resulting in strings
that explode on contact with browsers.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message