The + character is not a searchable token in the Search API, so your
search of "%2Bt" will only return results with a lone 't' in the
On Thu, Oct 1, 2009 at 11:41 PM, Gold <g...@evolved.net.nz> wrote:
> Hey all,
> I have a client that is wanting to use the plus character (+) as part
> of the search term for the REST based search.
> curl -s
> In this instance the %2B is the URL encoded +.
> When this is executed it returns many status messages where the one
> thing in common is the letter t appears in the message somewhere.
> A sample is here;
> All I can think of is that the search string is being url decoded
> twice. Once turns %2B into the + and the second turns the + into a
> I've posted a but for this but see that #924 is similar and was marked
> invalid Hopefully the extra info I provided makes the issue a little
> If anyone has seen this, or is affected by this could you please start
> the issue and comment if you have anything to add.
> If anyone has any suggestions to work around this I'd love to hear