[
https://issues.apache.org/jira/browse/SOLR-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875763#comment-13875763
]
Suneeta Mall commented on SOLR-5639:
------------------------------------
Hello Hoss,
Thanks a lot for looking into this issue. I agree with you that the correct
term to describe the 'http encoding' is html escaped. And also, when I
mentioned that other parameters works when url is html escaped, I was wrong. It
was a plugin that was formatting it for me. Apologies for that.
As per my understanding browsers support html escaped urls and so does most of
the web applications (even apache jira handle it (url
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=10&view=reporting&chart=burndownChart
=> please note its not browser thats doing the trick here, because I am
testing both the solar and apache jira in the same browser). However I could be
wrong.
I would like to look at forums, as suggested by you, and confirm that its okay
if Solr does not support html escaped urls before I could close the ticket.
Thanks a lot again.
> Return type parameter 'wt' is completely ignored when url is html escaped
> -------------------------------------------------------------------------
>
> Key: SOLR-5639
> URL: https://issues.apache.org/jira/browse/SOLR-5639
> Project: Solr
> Issue Type: Bug
> Components: query parsers, SearchComponents - other
> Affects Versions: 4.5.1
> Environment: Ubuntu 13.04,
> Browser Chrome
> Reporter: Suneeta Mall
>
> Querying solr with 'wt' parameter formats the result type as requested which
> works fine except when url is html escaped.
> For example:
> http://localhost:8983/solr/suggest?q=Status:ac&wt=json&indent=true
> the response I get is :
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">1</int>
> </lst>
> <lst name="spellcheck">
> <lst name="suggestions">
> <lst name="ac">
> <int name="numFound">5</int>
> <int name="startOffset">7</int>
> <int name="endOffset">9</int>
> <arr name="suggestion">
> <str>acknowledged</str>
> <str>ack</str>
> <str>actual</str>
> <str>actually</str>
> <str>access</str>
> </arr>
> </lst>
> <str name="collation">Status:acknowledged</str>
> </lst>
> </lst>
> </response>
> whereas the correct response should be:
> {
> "responseHeader":{
> "status":0,
> "QTime":1},
> "spellcheck":{
> "suggestions":[
> "ac",{
> "numFound":5,
> "startOffset":7,
> "endOffset":9,
> "suggestion":["acknowledged",
> "ack",
> "actual",
> "actually",
> "access"]},
> "collation","Status:acknowledged"]}}
> This causes severe problem when solr is integrated with GWT client where
> embedded script often encode url as per http encoding and ends up failing
> with timeout exception. Specially noticeable solr JSONP queries. for example:
> http://localhost:8983/solr/suggest?q=Status:ac&wt=json&indent=true&json.wrf=xyz
> when it returns xml instead of json.
> Noticeably other arguments works perfectly fine for example:
> http://localhost:8983/solr/suggest?q=Status:ac&wt=json&indent=true.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
