Hi Paul,
I just tested form the command line and everything seems fine
with: curl 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
If you are typing %20 into the IE address bar it is likely try to
correct your % (which is not a valid URL character) and making it %25
in the request but displaying it correctly to you. Try replacing it
with a + or a space and see what you get.
Thanks;
— Matt
On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:
Forgot to add, I am checking our client library now too.
Paul.
2009/3/3 Paul Kinlan <[email protected]>
Hi Matt,
I was typing the search term through IE (to test it after reports
that "" enclosed searches aren't working) as http://search.twitter.com/search.json?q=
"exeter city" which it then converts to http://search.twitter.com/search.json?q=
"exeter%20city" but the result came back as "%22exeter%2520city
%22" (see json object below) in the search API json object. It
works in firefox so I am presuming firefox is correctly encoding the
url.
{"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"?
since_id=1273765306&q=%22exeter%2520city%22","results_per_page":
15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}
it is highly likely that if IE is having the issue, the client API
would probably have it, however the query that is going out over the
wire (I checked with fiddler as "exeter%20city" and the result comes
back as above, so I don't think it is us for the entire problem).
Kind Regards,
Paul.
2009/3/3 Matt Sanford <[email protected]>
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
