[ https://issues.apache.org/jira/browse/SOLR-17263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847092#comment-17847092 ]
Andy Webb commented on SOLR-17263: ---------------------------------- Thanks [~dsmiley]! I'm happy with all the above, would say that's all we need to merge in for 9.6.1 here. https://github.com/apache/solr/pull/2454 could be included too subject to review, but it's just a refactoring so it can wait. > HttpJdkSolrClient doesn't encode curly braces etc > ------------------------------------------------- > > Key: SOLR-17263 > URL: https://issues.apache.org/jira/browse/SOLR-17263 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrJ > Affects Versions: 9.6.0 > Reporter: Andy Webb > Priority: Major > Fix For: 9.6.1 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Ref > https://issues.apache.org/jira/browse/SOLR-599?focusedCommentId=17842429#comment-17842429 > - {{HttpJdkSolrClient}} should use {{{}SolrParams{}}}' {{toQueryString()}} > method when constructing URLs to that all URL-unsafe characters are encoded. > It's implicitly using the {{toString()}} method currently which is intended > for logging etc purposes. > Attempting to use alternate query parsers in requests as shown below will > currently fail as the curly braces aren't encoded. > {noformat} > myquery.set("fq", "{!terms f=myfield}value1,value2"); {noformat} > -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org