Re: Issue with PHP urlencode and solr encoding

2014-02-23 Thread manju16832003
={!term%20f=model%20v="WBE(Honda%20Edix)"}*. I agree with Shawn comments that "Escaping query characters must be done before URL encoding." :-). Thanks again for your replies. -- View this message in context: http://lucene.472066.n3.nabble.com/Issue-with-PHP-urlenco

Re: Issue with PHP urlencode and solr encoding

2014-02-23 Thread Rico P
On Mon, Feb 24, 2014 at 11:52 AM, Shawn Heisey wrote: > > > The Solarium library for PHP also says that it does escaping, but I > can't find the manual section that they mention about term escaping. > Here's a section that has an example of phrase escaping (putting the > value in double quotes): >

Re: Issue with PHP urlencode and solr encoding

2014-02-23 Thread Shawn Heisey
On 2/23/2014 8:58 PM, manju16832003 wrote: > I come across the issue with urlencoding between PHP and Solr. > I have a field indexed with value *WBE(Honda Edix)* in Solr. > > From PHP codes, if I urlencode($string) and send to Solr, I do not get the > accurate results. > Here is the part of the so

Issue with PHP urlencode and solr encoding

2014-02-23 Thread manju16832003
/lucene.472066.n3.nabble.com/Issue-with-PHP-urlencode-and-solr-encoding-tp4119176.html Sent from the Solr - User mailing list archive at Nabble.com.