Re: [twitter-dev] Incorrect signature for users/search using REST API

2011-01-04 Thread Matt Harris
Hi Rohit, When passing spaces to in queries it is recommend you use %20. The reason is that the + is often badly encoded by OAuth libraries. Percent-encoding a space in the request is the most reliable way for the signature to be calculated. The reason why the search works for both Twitter_API

Re: [twitter-dev] Incorrect signature for users/search using REST API

2010-12-31 Thread Rohit Bansal
Hii Can you please share the code you are using through which you are getting the response. I am working this out using scribe in Java and able to fetch response for all API calls except possibly this one. Thanks On Thu, Dec 30, 2010 at 7:19 PM, deepa nagaraj deepa.23.naga...@gmail.comwrote:

[twitter-dev] Incorrect signature for users/search using REST API

2010-12-30 Thread Rohit Bansal
The XML response I am getting: ?xml version=1.0 encoding=UTF-8? hash request/1/users/search.xml?q=Twitter%20API/request errorIncorrect signature/error /hash Request for resource which I made: http://api.twitter.com/1/users/search.xml?q=Twitter%20API Request Type: GET Replacing

Re: [twitter-dev] Incorrect signature for users/search using REST API

2010-12-30 Thread deepa nagaraj
Hi... But i am getting same output for both url.. http://api.twitter.com/1/users/search.xml?q=Twitter%20API and http://api.twitter.com/1/users/search.xml?q=Twitter_API On Thu, Dec 30, 2010 at 7:00 PM, Rohit Bansal rohitbansal.h...@gmail.comwrote: The XML response I am getting: ?xml