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) Solr creates invalid jsonp strings
Date Mon, 16 May 2011 18:06:47 GMT

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

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

Fun happens when you specify something in json.wrf. This demands 'jsonp' instead of json,
which results in the result being treated as javascript, not json.  wt=json&json.wrf=SOME_PREFIX
will cause Solr to respond with

     SOME_PREFIX({whatever it was otherwise going to return})

instead of just

     {whatever it was otherwise going to return}

If there is then an interesting Unicode character in there, Chrome implodes and firefox quietly
rejects.



> Solr creates invalid jsonp strings
> ----------------------------------
>
>                 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