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 and Twitter%20API is
that matching is performed to the account name (not screen_name) loosely to
get as many results as possible.

Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Thu, Dec 30, 2010 at 7:09 AM, Rohit Bansal wrote:

> 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  > wrote:
>
>> 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 > > wrote:
>>
>>> The XML response I am getting:
>>>
>>> 
>>> 
>>>  /1/users/search.xml?q=Twitter%20API
>>>  Incorrect signature
>>> 
>>>
>>> Request for resource which I made:
>>> http://api.twitter.com/1/users/search.xml?q=Twitter%20API
>>>
>>> Request Type: GET
>>>
>>>
>>> Replacing Twitter%20API with Twitter_API is fetching me the correct
>>> response as stated in Twitter API documentation.
>>>
>>> If I am on the correct track then perhaps we need a correction in
>>> twitter documentation here, http://dev.twitter.com/doc/get/users/search.
>>>
>>>
>>> Please correct me if Twitter%20API should also be doing well. Besides
>>> this I also need to understand why underscore in Twitter_API works..?
>>>
>>> I have already posted this issue in Twitter API Issue tracker:
>>> http://code.google.com/p/twitter-api/issues/detail?id=2021
>>>
>>> --
>>> Twitter developer documentation and resources:
>>> http://dev.twitter.com/doc
>>> API updates via Twitter: http://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> http://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> http://groups.google.com/group/twitter-development-talk
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Deepa
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


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
wrote:

> 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 
> wrote:
>
>> The XML response I am getting:
>>
>> 
>> 
>>  /1/users/search.xml?q=Twitter%20API
>>  Incorrect signature
>> 
>>
>> Request for resource which I made:
>> http://api.twitter.com/1/users/search.xml?q=Twitter%20API
>>
>> Request Type: GET
>>
>>
>> Replacing Twitter%20API with Twitter_API is fetching me the correct
>> response as stated in Twitter API documentation.
>>
>> If I am on the correct track then perhaps we need a correction in
>> twitter documentation here, http://dev.twitter.com/doc/get/users/search.
>>
>>
>> Please correct me if Twitter%20API should also be doing well. Besides
>> this I also need to understand why underscore in Twitter_API works..?
>>
>> I have already posted this issue in Twitter API Issue tracker:
>> http://code.google.com/p/twitter-api/issues/detail?id=2021
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>
>
> --
> Regards,
>
> Deepa
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


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 wrote:

> The XML response I am getting:
>
> 
> 
>  /1/users/search.xml?q=Twitter%20API
>  Incorrect signature
> 
>
> Request for resource which I made:
> http://api.twitter.com/1/users/search.xml?q=Twitter%20API
>
> Request Type: GET
>
>
> Replacing Twitter%20API with Twitter_API is fetching me the correct
> response as stated in Twitter API documentation.
>
> If I am on the correct track then perhaps we need a correction in
> twitter documentation here, http://dev.twitter.com/doc/get/users/search.
>
>
> Please correct me if Twitter%20API should also be doing well. Besides
> this I also need to understand why underscore in Twitter_API works..?
>
> I have already posted this issue in Twitter API Issue tracker:
> http://code.google.com/p/twitter-api/issues/detail?id=2021
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>



-- 
Regards,

Deepa

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


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

2010-12-30 Thread Rohit Bansal
The XML response I am getting:



  /1/users/search.xml?q=Twitter%20API
  Incorrect signature


Request for resource which I made:
http://api.twitter.com/1/users/search.xml?q=Twitter%20API

Request Type: GET


Replacing Twitter%20API with Twitter_API is fetching me the correct
response as stated in Twitter API documentation.

If I am on the correct track then perhaps we need a correction in
twitter documentation here, http://dev.twitter.com/doc/get/users/search.


Please correct me if Twitter%20API should also be doing well. Besides
this I also need to understand why underscore in Twitter_API works..?

I have already posted this issue in Twitter API Issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=2021

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk