Hi Paul,
It sounds like whatever is generating your API requests is double
URL encoding. So the space becomes %20, and then on the second url
encoding the % becomes a %25.
Thanks;
— Matt Sanford / @mzsanford
On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
Hi,
I am noticing something that I think is odd at the moment.
Some of our users are not getting searches that are enclosed in
quotes via the API, yet they work directly from the website.
For example there is a difference between the following query on the
API and Website:
http://search.twitter.com/search?q=%22exeter%20city%22 which has the
same results as http://search.twitter.com/search?q=%22exeter+city%22
but returns a different result via the API using the following query
http://search.twitter.com/search.json?q="exeter%20city";
Looking at what is returned by the API the query looks like it has
been transformed in to "%22exeter%2520city%22". To me the %2520
looks odd when I would expect %20
Kind Regards,
Paul Kinlan
