Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 16 May 2011 18:56:48 +0000 (UTC)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <264609716.16149.1305572208236.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1556989509.14325.1305504347441.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2520) JSONResponseWriter w/json.wrf can
 produce invalid javascript depending on unicode chars in response data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yonik Seeley commented on SOLR-2520:
------------------------------------

It looks like we already escape \u2028 (see SOLR-1936), so we should just do the same for \u2029?

> 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